From: Nathan_Lynch@mentor.com (Nathan Lynch)
To: linux-arm-kernel@lists.infradead.org
Subject: Bulid regression with VDSO enabled
Date: Thu, 30 Apr 2015 09:38:00 -0500 [thread overview]
Message-ID: <55423E48.7000506@mentor.com> (raw)
In-Reply-To: <679194be9498c72543073a833e4a1719@agner.ch>
On 04/30/2015 06:44 AM, Stefan Agner wrote:
> OBJCOPY arch/arm/vdso/vdso.so
> BFD: arch/arm/vdso/vdso.so: Not enough room for program headers, try
> linking with -N
> arm-angstrom-linux-gnueabi-objcopy:arch/arm/vdso/vdso.so[.hash]: Bad
> value
> BFD: arch/arm/vdso/vdso.so: Not enough room for program headers, try
> linking with -N
> arm-angstrom-linux-gnueabi-objcopy:arch/arm/vdso/vdso.so: Bad value
> make[2]: *** [arch/arm/vdso/vdso.so] Error 1
> make[1]: *** [arch/arm/vdso] Error 2
> make[1]: *** Waiting for unfinished jobs....
>
> I'm using GCC 4.8.3 (Linaro GCC 4.8-2014.04) on Fedora 21. Any specific
> new requirements to the toolchain or a bug?
I've not encountered this before, and I'm not able to recreate it with
that toolchain.
If you're using the Linaro toolchain I would expect the name of objcopy
to be arm-linux-gnueabihf-objcopy, but your log shows
arm-angstrom-linux-gnueabi-objcopy. What's going on there?
next prev parent reply other threads:[~2015-04-30 14:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 11:44 Bulid regression with VDSO enabled Stefan Agner
2015-04-30 14:38 ` Nathan Lynch [this message]
2015-04-30 15:20 ` Stefan Agner
2015-04-30 15:48 ` Nathan Lynch
2015-04-30 15:58 ` Stefan Agner
2015-05-01 15:22 ` Nathan Lynch
[not found] ` <5548F302.5040909@mentor.com>
2015-05-05 17:27 ` support status of gold (was: Bulid regression with VDSO enabled) Russell King - ARM Linux
2015-05-05 17:28 ` Ard Biesheuvel
[not found] <391d6fc127b78ef4cbc5443557f0665a@agner.ch>
2015-05-08 11:28 ` Bulid regression with VDSO enabled Russell King - ARM Linux
2015-05-08 12:23 ` Stefan Agner
2015-05-08 15:27 ` Nathan Lynch
2015-05-08 16:08 ` Stefan Agner
2015-05-08 21:15 ` Nathan Lynch
2015-05-09 8:31 ` Ard Biesheuvel
2015-05-11 14:18 ` Nathan Lynch
2015-05-09 9:26 ` Russell King - ARM Linux
2015-05-15 17:01 ` Nathan Lynch
2015-05-09 12:41 ` Stefan Agner
2015-05-09 13:25 ` Stefan Agner
2015-05-11 14:27 ` Nathan Lynch
2015-05-09 9:32 ` Russell King - ARM Linux
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=55423E48.7000506@mentor.com \
--to=nathan_lynch@mentor.com \
--cc=linux-arm-kernel@lists.infradead.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 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.