From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751720Ab0BWIRw (ORCPT ); Tue, 23 Feb 2010 03:17:52 -0500 Received: from smtp2.it.da.ut.ee ([193.40.5.67]:47173 "EHLO smtp2.it.da.ut.ee" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751380Ab0BWIRu (ORCPT ); Tue, 23 Feb 2010 03:17:50 -0500 Date: Tue, 23 Feb 2010 10:17:48 +0200 (EET) From: Meelis Roos To: Linux Kernel list , linux-parisc@vger.lernel.org, linux-kbuild@vger.kernel.org Subject: CROSS_COMPILE not taken into account on parisc64? Message-ID: User-Agent: Alpine 1.00 (SOC 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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)