From: David Woodhouse <dwmw2@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, sam@ravnborg.org
Subject: Re: Firmware breakage
Date: Tue, 22 Jul 2008 14:31:04 -0400 [thread overview]
Message-ID: <1216751464.3019.29.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20080722190516.4ee477f4@lxorguk.ukuu.org.uk>
On Tue, 2008-07-22 at 19:05 +0100, Alan Cox wrote:
> On Tue, 22 Jul 2008 13:40:31 -0400
> David Woodhouse <dwmw2@infradead.org> wrote:
>
> > On Tue, 2008-07-22 at 17:34 +0100, Alan Cox wrote:
> > > If you crossbuild x86-32 on x86-64 and then attempt to do the install on
> > > an x86-32 box the install now breaks. This used to work until the
> > > firmware changes. Now you get
> > >
> > > /bin/sh: scripts/basic/fixdep: cannot execute binary file
> > >
> > > Fixdep should be built for the target platform surely ?
> >
> > Er, I haven't knowingly touched anything involving fixdep. Can you show
> > me exactly what you did? I'll try to reproduce and understand what's
> > happening.
>
> Build on a 64bit box with ARCH=i386
> NFS mount on a 32bit box
> make modules_install on 32bit box
>
> It used to work nicely, as of the firmware changes it doesn't. Not sure
> what the trigger is here yet.
Hm, I think it's because we're not building the firmware binaries until
modules_install time, and only _then_ do we want to build the ihex2fw
tool.
If you run 'make modules_install INSTALL_MOD_PATH=/tmp/foo' on the
x86_64 host first, does that fix it?
I was planning to build the firmware binaries as part of 'make modules'
anyway, because Rafael had related problems (not being able to write to
the NFS-exported kernel tree at all).
--
dwmw2
next prev parent reply other threads:[~2008-07-22 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 16:34 Alan Cox
2008-07-22 17:40 ` David Woodhouse
2008-07-22 18:05 ` Alan Cox
2008-07-22 18:31 ` David Woodhouse [this message]
2008-07-22 18:19 ` Alan Cox
2008-07-22 18:43 ` David Woodhouse
2008-07-22 18:51 ` David Woodhouse
2008-07-23 16:44 ` David Woodhouse
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=1216751464.3019.29.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--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®