From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-05-17
Date: Fri, 19 May 2017 03:29:16 +0200 [thread overview]
Message-ID: <20170519012916.GA6202@waldemar-brodkorb.de> (raw)
In-Reply-To: <20170518175758.6fb2c43d@free-electrons.com>
Hi Thomas,
Thomas Petazzoni wrote,
> Hello,
>
> > successes : 206
> > failures : 8
>
> Wowo!
>
> On 8 failures, we have:
>
> - 5 already fixed
> - 1 with a patch in progress
> - 2 that need investigation
>
> Looks good!
>
> On Thu, 18 May 2017 08:31:52 +0200 (CEST), Thomas Petazzoni wrote:
>
> > bfin | icu-58.2 | NOK | http://autobuild.buildroot.net/results/4828d9fc18283bda4c07af2c67f8ca9490dca28d | ORPH
>
> Toolchain issue:
>
> bfin-buildroot-linux-uclibc/bin/ld: LINKER BUG: .rofixup section size mismatch
>
> Waldemar, do you have an idea? Is this a recent regression?
We have seen this error in the past and we could fix it by applying
following patch:
https://git.busybox.net/buildroot/tree/package/binutils/2.26.1/0905-bfin-rofixup-bug.patch
It seems the workaround does not work when FDPIC + static +
-Wl,--gc-sections used. It seems icu is adding -Wl,--gc-sections
only in the static case on a Linux host.
This is a minor linker optimization.
How should we handle this? Patching configure.ac and autoreconf the
package?
best regards
Waldemar
prev parent reply other threads:[~2017-05-19 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 6:31 [Buildroot] [autobuild.buildroot.net] Build results for 2017-05-17 Thomas Petazzoni
2017-05-18 15:57 ` Thomas Petazzoni
2017-05-19 1:29 ` Waldemar Brodkorb [this message]
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=20170519012916.GA6202@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@busybox.net \
/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