From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Linux Kernel Development" <linux-kernel@vger.kernel.org>,
"Christian Bjølevik" <nafallo@magicalforest.se>,
"Deepak Saxena" <dsaxena@mvista.com>,
"Armin Kuster" <akuster@mvista.com>,
"Adrian Bunk" <bunk@kernel.org>
Subject: Re: kbuild: disable depmod in cross-compile kernel build
Date: Sun, 21 Oct 2007 19:53:43 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710211948450.6155@anakin> (raw)
In-Reply-To: <200710192259.l9JMxENl018922@hera.kernel.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1891 bytes --]
On Fri, 19 Oct 2007, Linux Kernel Mailing List wrote:
> Gitweb: http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=50a8ec31c3a00594ceb7c5f1dcf2ecdaf6a5b847
> Commit: 50a8ec31c3a00594ceb7c5f1dcf2ecdaf6a5b847
> Parent: 6f67a00498abf8f0b29c2cecfce188c70be309d0
> Author: Sam Ravnborg <sam@neptun.(none)>
> AuthorDate: Thu Oct 18 21:24:21 2007 +0200
> Committer: Sam Ravnborg <sam@neptun.(none)>
> CommitDate: Thu Oct 18 23:17:06 2007 +0200
>
> kbuild: disable depmod in cross-compile kernel build
>
> When building embedded systems in a cross-compile environment and
> populating a target's file system image, we don't want to run the
> depmod on the host as we may be building for a completely different
> architecture. Since there's no such thing as a cross-depmod, we
> just disable running depmod in the cross-compile case and we just
> run depmod on the target at bootup.
>
> Inspired by patches from Christian, Armin and Deepak.
>
> This solves: http://bugzilla.kernel.org/show_bug.cgi?id=3881
>
> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> Cc: Christian Bjølevik <nafallo@magicalforest.se>
> Cc: Deepak Saxena <dsaxena@mvista.com> and
> Cc: Armin Kuster <akuster@mvista.com>,
Euh, is these really necessary?
At work I have no problems running depmod on an i386 system for ppc64 modules
after I installed module-init-tools 3.3-pre2 (from Debian).
I did have problems (depmod SEGV) using the depmod that came with CentOS
4 (from module-init-tools 3.1-pre5).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next parent reply other threads:[~2007-10-21 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710192259.l9JMxENl018922@hera.kernel.org>
2007-10-21 17:53 ` Geert Uytterhoeven [this message]
2007-10-21 18:18 ` Frans Pop
2007-10-22 9:49 ` Sam Ravnborg
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=Pine.LNX.4.64.0710211948450.6155@anakin \
--to=geert@linux-m68k.org \
--cc=akuster@mvista.com \
--cc=bunk@kernel.org \
--cc=dsaxena@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nafallo@magicalforest.se \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®