From: Sam Ravnborg <sam@ravnborg.org>
To: Larry Finger <Larry.Finger@lwfinger.net>,
David Woodhouse <dwmw2@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Regression in 2.6.27-rc2 when cross-building the kernel
Date: Tue, 19 Aug 2008 06:48:54 +0200 [thread overview]
Message-ID: <20080819044854.GA2276@uranus.ravnborg.org> (raw)
In-Reply-To: <48A9FA05.9000601@lwfinger.net>
On Mon, Aug 18, 2008 at 05:39:01PM -0500, Larry Finger wrote:
> Sam Ravnborg wrote:
> >
> >Can you try do do a "make V=1 modules_install install" and post the
> >output up to and including the first call to fixdep.
> >
> >Neither of these targets should use fixdep and I assume it is
> >down in firmware/ but lets see.
And Larry log say it is so.
David - did you have a patch to fix this already?
[See details below]
Sam
>
> finger@mtech:/ide1/mtech/wireless-testing> sudo make V=1
> modules_install install
> make -f /ide1/mtech/wireless-testing/scripts/Makefile.modinst
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/arch/x86/crypto; cp
> arch/x86/crypto/aes-i586.ko
> /lib/modules/2.6.27-rc2-wl/kernel/arch/x86/crypto ; true
> /lib/modules/2.6.27-rc2-wl/kernel/arch/x86/crypto/aes-i586.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/crypto; cp
> crypto/aead.ko /lib/modules/2.6.27-rc2-wl/kernel/crypto ; true
> /lib/modules/2.6.27-rc2-wl/kernel/crypto/aead.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/crypto; cp
> crypto/aes_generic.ko /lib/modules/2.6.27-rc2-wl/kernel/crypto ; true
> /lib/modules/2.6.27-rc2-wl/kernel/crypto/aes_generic.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/crypto; cp
> crypto/anubis.ko /lib/modules/2.6.27-rc2-wl/kernel/crypto ; true
> /lib/modules/2.6.27-rc2-wl/kernel/crypto/anubis.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/crypto; cp
> crypto/arc4.ko /lib/modules/2.6.27-rc2-wl/kernel/crypto ; true
> /lib/modules/2.6.27-rc2-wl/kernel/crypto/arc4.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/crypto; cp
> crypto/authenc.ko /lib/modules/2.6.27-rc2-wl/kernel/crypto ; true
> /lib/modules/2.6.27-rc2-wl/kernel/crypto/authenc.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/crypto; cp
> crypto/blowfish.ko /lib/modules/2.6.27-rc2-wl/kernel/crypto ; true
> /lib/modules/2.6.27-rc2-wl/kernel/crypto/blowfish.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/crypto; cp
> crypto/cast5.ko /lib/modules/2.6.27-rc2-wl/kernel/crypto ; true
> /lib/modules/2.6.27-rc2-wl/kernel/crypto/cast5.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/crypto; cp
> crypto/cast6.ko /lib/modules/2.6.27-rc2-wl/kernel/crypto ; true
> /lib/modules/2.6.27-rc2-wl/kernel/crypto/cast6.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/crypto; cp crypto/cbc.ko
> /lib/modules/2.6.27-rc2-wl/kernel/crypto ; true
> /lib/modules/2.6.27-rc2-wl/kernel/crypto/cbc.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/crypto; cp
> crypto/crc32c.ko /lib/modules/2.6.27-rc2-wl/kernel/crypto ; true
> /lib/modules/2.6.27-rc2-wl/kernel/crypto/crc32c.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/crypto; cp
> crypto/crypto_blkcipher.ko /lib/modules/2.6.27-rc2-wl/kernel/crypto ;
> true /lib/modules/2.6.27-rc2-wl/kernel/crypto/crypto_blkcipher.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/crypto; cp
> crypto/crypto_null.ko /lib/modules/2.6.27-rc2-wl/kernel/crypto ; true
> /lib/modules/2.6.27-rc2-wl/kernel/crypto/crypto_null.ko
>
> -- snipped similar commands that were repeated --
>
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/sound/pci/ac97; cp
> sound/pci/ac97/snd-ac97-codec.ko
> /lib/modules/2.6.27-rc2-wl/kernel/sound/pci/ac97 ; true
> /lib/modules/2.6.27-rc2-wl/kernel/sound/pci/ac97/snd-ac97-codec.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/sound/pci; cp
> sound/pci/snd-es1938.ko /lib/modules/2.6.27-rc2-wl/kernel/sound/pci ;
> true /lib/modules/2.6.27-rc2-wl/kernel/sound/pci/snd-es1938.ko
> mkdir -p /lib/modules/2.6.27-rc2-wl/kernel/sound; cp
> sound/soundcore.ko /lib/modules/2.6.27-rc2-wl/kernel/sound ; true
> /lib/modules/2.6.27-rc2-wl/kernel/sound/soundcore.ko
> make -f /ide1/mtech/wireless-testing/scripts/Makefile.fwinst
> obj=firmware __fw_modinst
> gcc -Wp,-MD,firmware/.ihex2fw.d -Wall -Wstrict-prototypes -O2
> -fomit-frame-pointer -o firmware/ihex2fw firmware/ihex2fw.c
> /bin/sh: scripts/basic/fixdep: cannot execute binary file
> make[1]: *** [firmware/ihex2fw] Error 126
> make: *** [_modinst_post] Error 2
>
>
> As you suspected, it is when building firmware.
>
> Larry
next prev parent reply other threads:[~2008-08-19 4:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 2:38 Regression in 2.6.27-rc2 when cross-building the kernel Larry Finger
2008-08-18 19:32 ` Sam Ravnborg
2008-08-18 22:39 ` Larry Finger
2008-08-18 22:27 ` Alan Cox
2008-08-19 4:48 ` Sam Ravnborg [this message]
2008-08-19 7:48 ` David Woodhouse
2008-08-19 16:56 ` Larry Finger
2008-08-19 17:03 ` David Woodhouse
2008-08-19 19:25 ` Sam Ravnborg
2008-08-19 22:10 ` Larry Finger
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=20080819044854.GA2276@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=Larry.Finger@lwfinger.net \
--cc=dwmw2@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.