Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 5/5] binutils: Use tip of 2.26 branch
Date: Mon, 15 Feb 2016 14:30:49 +0000	[thread overview]
Message-ID: <1455546649.16142.419.camel@linuxfoundation.org> (raw)
In-Reply-To: <1455483171-66851-5-git-send-email-raj.khem@gmail.com>

On Sun, 2016-02-14 at 20:52 +0000, Khem Raj wrote:
> Until 2.26.1 is released there are few fixes which are needed
> especially
> when using -fpie, here are changes that are part of this version bump
> 
> H.J. Lu (7):
>       Add a testcase for PR ld/18591
>       Store estimated distances in compressed_size
>       Remove duplicated marker for 2.26 in gas/NEWS
>       Add -mrelax-relocations= to x86 assembler
>       Mask off the least significant bit in GOT offset
>       Enable -Bsymbolic and -Bsymbolic-functions to PIE
>       Fix a typo in objcopy manual
> 
> John David Anglin (1):
>       Fix /usr/bin/ld: final link failed: File truncated error on
> hppa

I think this is resulting in:

https://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/buil
ds/625/steps/BuildImages_1/logs/stdio

and

https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm-lsb/
builds/638/steps/BuildImages_1/logs/stdio

where config.log in one case says:

configure:4407: checking for C compiler default output file name
configure:4429: arm-poky-linux-gnueabi-gcc  -fstack-protector-strong -pie -fpie -D_FORTIFY_SOURCE=2 -O2 -pipe -g -feliminate-unused-debug-types --sysroot=/home/pokybuild/yoc
to-autobuilder/yocto-worker/nightly-arm-lsb/build/build/tmp/sysroots/beaglebone  -O2 -pipe -g -feliminate-unused-debug-types -fstack-protector-strong -pie -fpie -D_FORTIFY_S
OURCE=2  -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -fstack-protector-strong -Wl,-z,relro,-z,now conftest.c  >&5
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/build/build/tmp/sysroots/x86_64-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/5.3.0/ld: 
error: a.out uses VFP register arguments, /tmp/ccbzGaSi.o does not
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/build/build/tmp/sysroots/x86_64-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/5.3.0/ld: failed to merge target specific data of file /tmp/ccbzGaSi.o
collect2: error: ld returned 1 exit status

Cheers,

Richard


  reply	other threads:[~2016-02-15 14:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14 20:52 [PATCH 1/5] musl: Upgrade to tip of tree Khem Raj
2016-02-14 20:52 ` [PATCH 2/5] security_flags: Add SECURITY_CFLAGS to TARGET_CC_ARCH for binutils Khem Raj
2016-02-14 20:52 ` [PATCH 3/5] rpm: Fix build with musl Khem Raj
2016-02-14 20:52 ` [PATCH 4/5] valgrind: " Khem Raj
2016-02-14 20:52 ` [PATCH 5/5] binutils: Use tip of 2.26 branch Khem Raj
2016-02-15 14:30   ` Richard Purdie [this message]
2016-02-15 15:33     ` Khem Raj
2016-02-15 17:04       ` Khem Raj
2016-02-15 17:19         ` Richard Purdie

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=1455546649.16142.419.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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