Regression in 2.6.27-rc2 when cross-building the kernel
One of my i386 systems used just for testing can take up to 18 hours to build a new kernel with about 200 modules. When performing a bisection, this gets rather tedious. As a result, I moved the kernel sources to an NFS volume, do the majority of the work as a cross-build on my x86_64 computer, and only switch to the slow machine to install the kernel and modules. Somewhere between 2.6.27-rc1 and -rc2, the module installation broke because the build leaves scripts/basic/fixdep as a 64-bit program that will not run on the 32-bit system. Once I get to the i386 machine, I delete the two programs from scripts/basic/, manually rebuild them with a 'make scripts/basic/' and then do the final 'make modules_install install'.
Larry
Quoted 11 lines · Larry Finger
One of my i386 systems used just for testing can take up to 18 hours to build a new kernel with about 200 modules. When performing a bisection, this gets rather tedious. As a result, I moved the kernel sources to an NFS volume, do the majority of the work as a cross-build on my
x86_64computer, and only switch to the slow machine to install the kernel and modules. Somewhere between 2.6.27-rc1 and -rc2, the module installation broke because the build leavesscripts/basic/fixdepas a 64-bit program that will not run on the 32-bit system. Once I get to the i386 machine, I delete the two programs fromscripts/basic/, manually rebuild them with a 'makescripts/basic/' and then do the final 'makemodules_installinstall'.
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.
Thanks,
Sam
Quoted 5 lines · Sam Ravnborg
Can you try do do a "make V=1
modules_installinstall" 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.
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; cparch/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpsound/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; cpsound/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; cpsound/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
Quoted 5 lines
gcc -Wp,-MD,firmware/.ihex2fw.d -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -ofirmware/ihex2fwfirmware/ihex2fw.c/bin/sh:scripts/basic/fixdep: cannot execute binary file make[1]: *** [firmware/ihex2fw] Error 126
make: *** [_modinst_post] Error 2
Ditto here when building ARCH=i386 on 64bit then NFS doing "make modules_install". Also breaks if the NFS mount is ro
Quoted 7 lines · Larry Finger
Quoted 6 lines · Sam Ravnborg
Can you try do do a "make V=1
modules_installinstall" 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
Quoted 69 lines
finger@mtech:/ide1/mtech/wireless-testing> sudo make V=1
modules_installinstall
make -f /ide1/mtech/wireless-testing/scripts/Makefile.modinst
mkdir -p/lib/modules/2.6.27-rc2-wl/kernel/arch/x86/crypto; cparch/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpcrypto/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; cpsound/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; cpsound/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; cpsound/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 -ofirmware/ihex2fwfirmware/ihex2fw.c/bin/sh:scripts/basic/fixdep: cannot execute binary file make[1]: *** [firmware/ihex2fw] Error 126
make: *** [_modinst_post] Error 2As you suspected, it is when building firmware.
Larry
Quoted 4 lines · Sam Ravnborg
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?
Signature · 2 lines
David Woodhouse Open Source Technology Centre [email protected] Intel Corporation
Quoted 11 lines · David Woodhouse
Quoted 3 lines · Sam Ravnborg
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_installtime. 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
Larry
Quoted 6 lines · Larry Finger
Quoted 5 lines · David Woodhouse
Quoted 3 lines · Sam Ravnborg
And Larry log say it is so.
David - did you have a patch to fix this already?
Quoted 8 lines
Quoted 6 lines
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_installtime. That went in a while ago though.Why is ihex2fw being rebuilt?
sudo make V=2
modules_installsays:
Yeah, but why does anything require ihex2fw in the first place?
Signature · 2 lines
David Woodhouse Open Source Technology Centre [email protected] Intel Corporation
Quoted 15 lines · Larry Finger
Quoted 11 lines · David Woodhouse
Quoted 3 lines · Sam Ravnborg
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_installtime. That went in a while ago though.Why is ihex2fw being rebuilt?
sudo make V=2
modules_installsays:
Quoted 8 lines
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
Quoted 10 lines · Sam Ravnborg
Quoted 7 lines · Larry Finger
sudo make V=2
modules_installsays: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 2Do you have some logging info before we start to build ihex2fw?
Only one line like these for each of the modules, followed immediately by the build of ihex2fw:
INSTALL sound/core/snd.ko - due to target is PHONY
INSTALL sound/drivers/mpu401/snd-mpu401-uart.ko - due to target is
PHONY
INSTALL sound/drivers/mpu401/snd-mpu401.ko - due to target is PHONY
INSTALL sound/drivers/opl3/snd-opl3-lib.ko - due to target is PHONY
INSTALL sound/drivers/opl3/snd-opl3-synth.ko - due to target is PHONY
INSTALL sound/pci/ac97/snd-ac97-codec.ko - due to target is PHONY
INSTALL sound/pci/snd-es1938.ko - due to target is PHONY
INSTALL sound/soundcore.ko - due to target is PHONY
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
Larry