From: Keith Owens <kaos@ocs.com.au>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Cross Compiling
Date: Tue, 17 Feb 2004 00:51:27 +1100 [thread overview]
Message-ID: <5233.1076939487@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 15 Feb 2004 18:38:36 BST." <20040215173835.GA22567@MAIL.13thfloor.at>
On Sun, 15 Feb 2004 18:38:36 +0100,
Herbert Poetzl <herbert@13thfloor.at> wrote:
>On Sun, Feb 15, 2004 at 12:16:10PM +0100, Geert Uytterhoeven wrote:
>> One related question: anyone who knows how to run a cross-depmod,
>> so I can find missing symbol exports without running depmod
>> on the target?
>
>../modutils-2.4.26/configure --target=m68k-linux
>
>seems to do something, so it might even work ...
>
>depmod: ELF file /lib/.../kernel/crypto/aes.o not for this architecture
>depmod: ELF file /lib/.../kernel/crypto/blowfish.o not for this architecture
modutils <= 2.4 was never designed to run in cross compile mode. The
modules.dep file created at compile time is a courtesy file, in an
attempt to avoid warning messages (no modules.dep) on the very first
boot of a new kernel version. Once the kernel has been booted, it ahs
its own modules.dep.
Making it run on the target system but handle cross compiled modules
pulls in all the problems associated with build and target having
different word sizes, different endianess and different object
information. modutils 2.4 is now in stable mode, it is only taking bug
fixes. A complete rewrite to handle cross compile is not a bug fix.
Bottom line: when building cross compile use make ... DEPMOD=/bin/true
to avoid using the local depmod.
next prev parent reply other threads:[~2004-02-16 14:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040213205743.GA30245@MAIL.13thfloor.at.suse.lists.linux.kernel>
2004-02-13 21:25 ` Kernel Cross Compiling Andi Kleen
2004-02-13 21:46 ` Herbert Poetzl
2004-02-13 23:45 ` Herbert Poetzl
2004-02-15 11:16 ` Geert Uytterhoeven
2004-02-15 17:38 ` Herbert Poetzl
2004-02-16 13:51 ` Keith Owens [this message]
2004-02-17 21:51 Judith Lebzelter
2004-02-18 7:19 ` Herbert Poetzl
-- strict thread matches above, loose matches on Subject: below --
2004-02-14 21:03 Dan Kegel
2004-02-14 22:07 ` Herbert Poetzl
2004-02-15 3:51 ` Dan Kegel
2004-02-14 3:26 Stephen M. Kenton
2004-02-14 14:21 ` Herbert Poetzl
2004-02-15 23:28 ` Robert Schwebel
2004-02-15 23:59 ` William Lee Irwin III
2004-02-13 20:57 Herbert Poetzl
2004-02-13 21:31 ` David Mosberger
2004-02-13 21:44 ` Herbert Poetzl
2004-02-14 0:58 ` David Mosberger
2004-02-14 1:08 ` Herbert Poetzl
2004-02-14 2:35 ` Herbert Poetzl
2004-02-14 2:51 ` David Mosberger
2004-02-16 22:50 ` Jim Wilson
2004-02-16 0:03 ` Peter Chubb
2004-02-14 8:32 ` Timothy D. Witham
2004-02-14 13:03 ` Herbert Poetzl
2004-02-14 19:25 ` Timothy D. Witham
2004-02-14 22:08 ` Herbert Poetzl
2004-02-16 21:41 ` cliff white
2004-02-16 22:10 ` Herbert Poetzl
2004-02-17 13:26 ` Maciej W. Rozycki
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=5233.1076939487@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=geert@linux-m68k.org \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
/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