* CROSS_COMPILE not taken into account on parisc64?
@ 2010-02-23 8:17 Meelis Roos
2010-02-23 11:19 ` Michal Marek
0 siblings, 1 reply; 3+ messages in thread
From: Meelis Roos @ 2010-02-23 8:17 UTC (permalink / raw)
To: Linux Kernel list, linux-parisc, linux-kbuild
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 tells
CONFIG_64BIT=y
CONFIG_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?
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: CROSS_COMPILE not taken into account on parisc64?
2010-02-23 8:17 CROSS_COMPILE not taken into account on parisc64? Meelis Roos
@ 2010-02-23 11:19 ` Michal Marek
2010-02-23 11:33 ` Meelis Roos
0 siblings, 1 reply; 3+ messages in thread
From: Michal Marek @ 2010-02-23 11:19 UTC (permalink / raw)
To: Meelis Roos; +Cc: Linux Kernel list, linux-parisc, linux-kbuild
On 23.2.2010 09:17, Meelis Roos wrote:
> 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
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.
[...]
> However, I see no inclusion of arch-specific Makefile before the
> assignment of OBJCOPY in main Makefile. Could this be the problem?
That's OK, make variables assigned with '=' are expanded when they are used.
Michal
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-02-23 11:33 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-23 8:17 CROSS_COMPILE not taken into account on parisc64? Meelis Roos
2010-02-23 11:19 ` Michal Marek
2010-02-23 11:33 ` Meelis Roos
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.