CROSS_COMPILE not taken into account on parisc64?
I am trying to build 2.6.33-rc* for a 64-bit parisc machine (using kernel.package in Debian unstable if it matters). The build fails assembling any .ko files with objcopy:
objcopy --add-gnu-debuglink=/home/mroos/linux-2.6/debian/linux-image-2.6.33-rc8-00173-g627fa17/usr/lib/debug/lib/modules/2.6.33-rc8-00173-g627fa17/kernel/drivers/cdrom/cdrom.ko /home/mroos/linux-2.6/debian/linux-image-2.6.33-rc8-00173-g627fa17/lib/modules/2.6.33-rc8-00173-g627fa17/kernel/drivers/cdrom/cdrom.ko objcopy:/home/mroos/linux-2.6/debian/linux-image-2.6.33-rc8-00173-g627fa17/lib/modules/2.6.33-rc8-00173-g627fa17/kernel/drivers/cdrom/cdrom.ko: File format not recognized
Trying hppa64-linux-gnu-objcopy by hand works - but we should be using this cross compile prefix automatically.
We do have
OBJDUMP = $(CROSS_COMPILE)objdump
in main Makefile, and
ifdef CONFIG_64BIT
UTS_MACHINE := parisc64 CHECKFLAGS += -D__LP64__=1 -m64 WIDTH := 64 CROSS_COMPILE := hppa64-linux-gnu-
else # 32-bit
WIDTH :=
endif
in arch/parisc/Makefile so it seems OK at the first glance.
grep 64BIT .config tellsCONFIG_64BIT=yCONFIG_PHYS_ADDR_T_64BIT=y
so this is correct too.
However, I see no inclusion of arch-specific Makefile before the assignment of OBJCOPY in main Makefile. Could this be the problem?
Signature · 1 line
Meelis Roos ([email protected])
Quoted 6 lines · Meelis Roos
I am trying to build 2.6.33-rc* for a 64-bit parisc machine (using kernel.package in Debian unstable if it matters). The build fails assembling any .ko files with objcopy:
objcopy --add-gnu-debuglink=/home/mroos/linux-2.6/debian/linux-image-2.6.33-rc8-00173-g627fa17/usr/lib/debug/lib/modules/2.6.33-rc8-00173-g627fa17/kernel/drivers/cdrom/cdrom.ko
/home/mroos/linux-2.6/debian/linux-image-2.6.33-rc8-00173-g627fa17/lib/modules/2.6.33-rc8-00173-g627fa17/kernel/drivers/cdrom/cdrom.koobjcopy:/home/mroos/linux-2.6/debian/linux-image-2.6.33-rc8-00173-g627fa17/lib/modules/2.6.33-rc8-00173-g627fa17/kernel/drivers/cdrom/cdrom.ko: File format not recognized
I guess this objcopy command is run outside of the kernel build system (a packaging script storing debug info in /usr/lib/debug), nothing the kernel makefiles can do about.
[...]
Quoted 2 lines
However, I see no inclusion of arch-specific
Makefilebefore the assignment of OBJCOPY in mainMakefile. Could this be the problem?
That's OK, make variables assigned with '=' are expanded when they are used.
Michal
Quoted 3 lines
I guess this objcopy command is run outside of the kernel build system (a packaging script storing debug info in
/usr/lib/debug), nothing the kernel makefiles can do about.
Thanks - my bad that I didn't notice this.
Signature · 1 line
Meelis Roos ([email protected])