public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: cross-compiling a kernel, was: Re: running Speakup on the Mac
Date: Wed, 12 Apr 2006 11:01:46 -0700	[thread overview]
Message-ID: <20060412180146.GA29254@localhost.localdomain> (raw)
In-Reply-To: <OFB30E238D.F2F8603E-ON0725714E.005EC8F8-0725714E.005F2C20@usgs.gov>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

You first either get a pre-compiled tool chain, or you build your own,
which is not as bad as it sounds, just be sure you have a very fast
system, and have something else to do while your machine does its
thing.

Now, assuming you wanted to for example go through make config for the
x86_64 architecture, you'd do:

make ARCH=x86_64 config

Doing make modules, and make modules_install would go the same way. As
for building the actual kernel, that seems to differ from target to
target. For some targets, you do make linux, for others you do make,
and probably for some you do something else.

Someone once told me that the tool chain that comes with modern
gnu/linux distributions is ready to cross-compile for all other
supported targets, but I don't know if that's true or not. Hth.

Greg




On Wed, Apr 12, 2006 at 10:19:34AM -0700, Sean M McMahon wrote:
> some have also made efforts to make emacspeak run on the mac.  Consolte 
> the emacspeak list to see if they were successful.  My tangental question 
> to this thread is how to you roll your own kernels for such platforms as 
> the mac or 64-bit systems?  I didn't see this explained in the kernel 
> howto and I didn't se an explanation on how to cross-compile a kernel.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFEPUCK7s9z/XlyUyARAlmCAKCkZ33uAg7ZIrUavJCu++Z4ztuPHQCfQ5B8
o9NypFkiQkZxZm4IshrqNr4=
=I3PH
-----END PGP SIGNATURE-----


  reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jane Jordan (gmail)
 ` Jacob Schmude
   ` Jane Jordan (gmail)
     ` bob
   ` Sean M McMahon
     ` Gregory Nowak [this message]
       ` cross-compiling a kernel, was: " Igor Gueths
         ` Gregory Nowak
           ` Igor Gueths
 ` ace
 ` Luke Yelavich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060412180146.GA29254@localhost.localdomain \
    --to=greg@romuald.net.eu.org \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).