From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Cc: kai.germaschewski@gmx.de
Subject: 2.5.42 broke ARM zImage/Image
Date: Sat, 12 Oct 2002 12:32:56 +0100 [thread overview]
Message-ID: <20021012123256.C12955@flint.arm.linux.org.uk> (raw)
Hi,
I'm trying to get 2.5.42 to build on ARM, and I've finally run out of
ideas for things to try to get arch/arm/boot/Makefile and
arch/arm/boot/compressed/Makefile to work correctly.
What I'm seeing is:
/home/rmk/bin/arm-linux-ld -p -X -T vmlinux.lds head.o misc.o piggy.o /home/rmk/arm-linux/lib/gcc-lib/arm-linux/2.95.3/libgcc.a -o vmlinux
/home/rmk/bin/arm-linux-ld:vmlinux.lds:14: parse error
make[2]: *** [vmlinux] Error 1
make[1]: *** [compressed/vmlinux] Error 2
make: *** [zImage] Error 2
This appears to be because ZRELADDR is not passed from arch/arm/boot/Makefile
to arch/arm/boot/compressed/Makefile. You may think this is fairly trivial
to fix, just export it. However, it is already exported with a bunch of
other symbols. Other symbols seem to make it through to compressed/Makefile
though.
I've tried many things, like including $(TOPDIR) Rules.make at the top of
arch/arm/boot/Makefile, but this doesn't seem to make any difference what
so ever.
Help!
Unless this can be solved, I'm going to be pushing _compile only_ tested
stuff to Linus in the forthcoming weeks until someone can provide some
hints as to what and why this broke.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next reply other threads:[~2002-10-12 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 11:32 Russell King [this message]
2002-10-12 21:38 ` 2.5.42 broke ARM zImage/Image Sam Ravnborg
2002-10-14 23:22 ` Russell King
2002-10-15 15:22 ` Sam Ravnborg
2002-10-15 15:30 ` Kai Germaschewski
2002-10-15 19:25 ` Sam Ravnborg
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=20021012123256.C12955@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=kai.germaschewski@gmx.de \
--cc=linux-kernel@vger.kernel.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