From: Michal Marek <mmarek@suse.cz>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-parisc@vger.lernel.org, linux-kbuild@vger.kernel.org
Subject: Re: CROSS_COMPILE not taken into account on parisc64?
Date: Tue, 23 Feb 2010 12:19:30 +0100 [thread overview]
Message-ID: <4B83B9C2.8040500@suse.cz> (raw)
In-Reply-To: <alpine.SOC.1.00.1002231008460.18041@math.ut.ee>
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
next prev parent reply other threads:[~2010-02-23 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 8:17 CROSS_COMPILE not taken into account on parisc64? Meelis Roos
2010-02-23 11:19 ` Michal Marek [this message]
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=4B83B9C2.8040500@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.lernel.org \
--cc=mroos@linux.ee \
/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 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.