From: Sam Ravnborg <sam@ravnborg.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: David Woodhouse <dwmw2@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Regression in 2.6.27-rc2 when cross-building the kernel
Date: Tue, 19 Aug 2008 21:25:08 +0200 [thread overview]
Message-ID: <20080819192508.GA6774@uranus.ravnborg.org> (raw)
In-Reply-To: <48AAFB4C.1030300@lwfinger.net>
On Tue, Aug 19, 2008 at 11:56:44AM -0500, Larry Finger wrote:
> David Woodhouse wrote:
> >On Tue, 2008-08-19 at 06:48 +0200, Sam Ravnborg wrote:
> >>And Larry log say it is so.
> >>
> >>David - did you have a patch to fix this already?
> >
> >The fix was to 'build' the firmware blobs at the same time as 'make
> >modules', so that they're already built and don't need to be built at
> >modules_install time. That went in a while ago though.
> >
> >Why is ihex2fw being rebuilt?
> >
>
> sudo make V=2 modules_install says:
>
> HOSTCC firmware/ihex2fw - due to: /usr/include/gnu/stubs-64.h
> /usr/lib64/gcc/x86_64-suse-linux/4.3/include/stddef.h
> /usr/lib64/gcc/x86_64-suse-linux/4.3/include-fixed/limits.h
> /usr/lib64/gcc/x86_64-suse-linux/4.3/include-fixed/syslimits.h
> /usr/lib64/gcc/x86_64-suse-linux/4.3/include/stdarg.h
> /bin/sh: scripts/basic/fixdep: cannot execute binary file
> make[1]: *** [firmware/ihex2fw] Error 126
> make: *** [_modinst_post] Error 2
Do you have some logging info before we start to build ihex2fw?
Sam
next prev parent reply other threads:[~2008-08-19 21:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 2:38 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
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 [this message]
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=20080819192508.GA6774@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome