linux-kernel - CROSS_COMPILE not taken into account on parisc64?

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-next>] [day] [month] [year] [list]

Message-ID: <alpine.SOC.1.00.1002231008460.18041@math.ut.ee>
Date:	Tue, 23 Feb 2010 10:17:48 +0200 (EET)
From:	Meelis Roos <mroos@...ux.ee>
To:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	linux-parisc@...r.lernel.org, linux-kbuild@...r.kernel.org
Subject: 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 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@...ux.ee)
--
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/