Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] mpd: fix build on SPARC
Date: Fri, 12 Feb 2016 22:17:05 +0100	[thread overview]
Message-ID: <20160212221705.432ba378@free-electrons.com> (raw)
In-Reply-To: <56BE4590.8070803@mind.be>

Arnout,

On Fri, 12 Feb 2016 21:50:24 +0100, Arnout Vandecappelle wrote:

> > However, with an external musl toolchain built with Buildroot no
> > libatomic.so will be installed on the target, it only exists in
> > sysroot:
> > 
> >     $ find output/ -type f -name "libatomic.so*"
> >     output/host/usr/arm-buildroot-linux-
> >     musleabi/sysroot/lib/libatomic.so.1.1.0
> 
>  I wonder if we shouldn't just copy all the libraries for the external
> toolchains. If you're using an external toolchain, you probably don't care about
> size too much. Or you'd use a buildroot-built external toolchain, and in that
> case really everything is needed.

I really don't see why users of external toolchains would not care
about size.

However, libatomic is pretty much as essential as libgcc is, so we
should definitely add it to the libraries that should always be copied.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-02-12 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 21:02 [Buildroot] [git commit] mpd: fix build on SPARC Thomas Petazzoni
2016-02-11 11:12 ` Jörg Krause
2016-02-12 20:50   ` Arnout Vandecappelle
2016-02-12 21:17     ` 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=20160212221705.432ba378@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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