linux-kernel - Re: Firmware breakage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 22 Jul 2008 19:05:16 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	linux-kernel@...r.kernel.org, sam@...nborg.org
Subject: Re: Firmware breakage

On Tue, 22 Jul 2008 13:40:31 -0400
David Woodhouse <dwmw2@...radead.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.

If I hand rebuild fixdep as a 32bit binary the rest runs through fine.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/