From: Carlos Munoz <carlos@kenati.com>
To: sknauert@wesleyan.edu
Cc: linux-mips@linux-mips.org
Subject: Re: Cross-Compile difficulties
Date: Tue, 22 May 2007 16:26:39 -0700 [thread overview]
Message-ID: <46537C2F.6010000@kenati.com> (raw)
In-Reply-To: <51450.129.133.92.31.1179873846.squirrel@webmail.wesleyan.edu>
sknauert@wesleyan.edu wrote:
> make CROSS_COMPILE=mips-linux-gnu- oldconfig
> make -j 3 CROSS_COMPILE=mips-linux-gnu- all
> make CROSS_COMPILE=mips-linux-gnu- INSTALL_MOD_PATH=~/ modules_install
> cp vmlinux ~/boot/vmlinux-2.6.21.1
> cp System.map ~/boot/System.map-2.6.21.1
> cp .config ~/boot/config-2.6.21.1
> cd ~/
> tar -cf kernel.tar lib boot
>
Don't know if it makes any difference, but I always specify the
architecture on the command line:
make ARCH=mips -j 3 CROSS_COMPILE=mips-linux-gnu all
next prev parent reply other threads:[~2007-05-22 23:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1178743456.15447.41.camel@scarafaggio>
[not found] ` <20070516151939.GH19816@deprecation.cyrius.com>
[not found] ` <20070516160313.GA3409@bongo.bofh.it>
[not found] ` <50621.192.168.2.50.1179383217.squirrel@eppesuigoccas.homedns.org>
2007-05-17 15:16 ` SGI O2 meth: missing sysfs device symlink Martin Michlmayr
2007-05-21 15:47 ` Ralf Baechle
2007-05-22 11:09 ` Ralf Baechle
2007-05-22 11:41 ` Giuseppe Sacco
2007-05-22 12:01 ` sknauert
2007-05-22 12:28 ` Ralf Baechle
2007-05-22 13:32 ` sknauert
2007-05-22 15:18 ` Thiemo Seufer
2007-05-22 16:46 ` Cross-Compile difficulties sknauert
2007-05-22 17:32 ` Geert Uytterhoeven
2007-05-22 22:44 ` sknauert
2007-05-22 23:26 ` Carlos Munoz [this message]
2007-05-23 3:42 ` Kumba
2007-05-23 17:41 ` sknauert
2007-05-23 6:12 ` Geert Uytterhoeven
2007-05-22 13:02 ` SGI O2 meth: missing sysfs device symlink Thiemo Seufer
2007-05-22 12:13 ` Giuseppe Sacco
2007-05-22 13:00 ` Ralf Baechle
2007-05-23 11:45 ` Giuseppe Sacco
2007-05-24 11:47 ` Ralf Baechle
2007-05-23 3:51 ` Kumba
2007-05-23 8:37 ` Ralf Baechle
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=46537C2F.6010000@kenati.com \
--to=carlos@kenati.com \
--cc=linux-mips@linux-mips.org \
--cc=sknauert@wesleyan.edu \
/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