Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libaio: Link against libgcc and libc to avoid unresolved symbols
Date: Mon, 8 Oct 2018 21:35:43 +0200	[thread overview]
Message-ID: <20181008213543.24480f1f@windsurf> (raw)
In-Reply-To: <20180928133734.2352-1-abrodkin@synopsys.com>

Hello,

On Fri, 28 Sep 2018 16:37:34 +0300, Alexey Brodkin wrote:
> Fix proposed by Debian developers that makes sure all libgcc.a
> sybols used in libaio.so are built-in.
> 
> Fixes build failures of blktrace, lvm2 and the like users of libaio.
> 
> A couple of examples below:
> blktrace: http://autobuild.buildroot.net/results/5528ab59f1939a7eff7e85318f3b36283019cc50/
> lvm2:     http://autobuild.buildroot.net/results/a5dfc87f94b97135e5cc84f6a876114891ed9dd9/
> 
> And since we solve the problem in libaio sources there's no need to
> mess with compilation flags in Buildroot, thus partially revert
> commit ce6536ae500f ("libaio: work-around for PowerPC issue").
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> ---
>  ...gainst-libgcc-to-avoid-unresolved-symbols.patch | 57 ++++++++++++++++++++++
>  package/libaio/libaio.mk                           |  6 ---
>  2 files changed, 57 insertions(+), 6 deletions(-)
>  create mode 100644 package/libaio/0003-Link-against-libgcc-to-avoid-unresolved-symbols.patch

Applied to master with a slightly tweaked commit log. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-10-08 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28 13:37 [Buildroot] [PATCH] libaio: Link against libgcc and libc to avoid unresolved symbols Alexey Brodkin
2018-10-08 19:35 ` Thomas Petazzoni [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=20181008213543.24480f1f@windsurf \
    --to=thomas.petazzoni@bootlin.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