From: Meelis Roos <mroos@linux.ee>
To: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-parisc@vger.lernel.org, linux-kbuild@vger.kernel.org
Subject: CROSS_COMPILE not taken into account on parisc64?
Date: Tue, 23 Feb 2010 10:17:48 +0200 (EET) [thread overview]
Message-ID: <alpine.SOC.1.00.1002231008460.18041@math.ut.ee> (raw)
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)
next reply other threads:[~2010-02-23 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 8:17 Meelis Roos [this message]
2010-02-23 11:19 ` Michal Marek
2010-02-23 11:33 ` Meelis Roos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.SOC.1.00.1002231008460.18041@math.ut.ee \
--to=mroos@linux.ee \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.lernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®