From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] Update libaio to 0.3.110
Date: Sat, 2 Apr 2016 17:53:40 +0200 [thread overview]
Message-ID: <56FFEB04.9090800@gmail.com> (raw)
In-Reply-To: <1455824391-23524-1-git-send-email-alistair.francis@xilinx.com>
Hi Alistair, Thomas, All,
Le 18/02/2016 20:39, Alistair Francis a ?crit :
> Update libaio from 0.3.108 to 0.3.110. This adds AArch64 support.
>
> Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
> ---
> package/libaio/0001-arches.patch | 454 ++-------------------------------------
> package/libaio/Config.in | 2 +-
> package/libaio/libaio.hash | 4 +-
> package/libaio/libaio.mk | 2 +-
> 4 files changed, 20 insertions(+), 442 deletions(-)
>
Since the libaio bump, the blktrace package is broken on powerpc [1].
/home/peko/autobuild/instance-1/output/host/usr/bin/powerpc-linux-gnu-gcc
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -I. -I..
-I../btt -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -UCOUNT_IOS
-UDEBUG -DNDEBUG -o btreplay btreplay.o -laio -lrt -lpthread
[...]ld: btreplay: hidden symbol `_restgpr_29_x' in [..]libgcc.a(crtresxgpr.o)
is referenced by DSO
[...]ld: final link failed: Nonrepresentable section on output
It's seems that only powerpc is affected by this issue...
I'm not sure about a proper fixes but adding -shared to the command line fixes
the build (not runtime tested though).
Can you take a look ?
Best regards,
Romain Naour
[1] http://autobuild.buildroot.net/?reason=blktrace-1.1.0
next prev parent reply other threads:[~2016-04-02 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 19:39 [Buildroot] [PATCH v3] Update libaio to 0.3.110 Alistair Francis
2016-02-20 22:49 ` Arnout Vandecappelle
2016-02-22 17:51 ` Alistair Francis
2016-02-21 14:37 ` Thomas Petazzoni
2016-02-22 17:52 ` Alistair Francis
2016-04-02 15:53 ` Romain Naour [this message]
2016-04-05 0:41 ` Alistair Francis
2016-04-05 0:46 ` Alistair Francis
2016-04-14 21:45 ` Alistair Francis
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=56FFEB04.9090800@gmail.com \
--to=romain.naour@gmail.com \
--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