From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] cc-tool: pass -latomic in LIBS
Date: Wed, 23 Aug 2017 23:24:37 +0200 [thread overview]
Message-ID: <20170823232437.64b5b82a@windsurf> (raw)
In-Reply-To: <20170820133416.11231-1-thomas.petazzoni@free-electrons.com>
Hello,
On Sun, 20 Aug 2017 15:34:15 +0200, Thomas Petazzoni wrote:
> Just like -lpthread was passed in LIBS, -latomic should also be passed
> in LIBS. In order for this to work, we however need to first fix
> cc-tool's Makefile.am so that it does not overwrite LIBS.
>
> This is the first part of fixing the build of cc-tool in a static
> linking scenario on SPARC, i.e to fix:
>
> http://autobuild.buildroot.net/results/ed9f2524d0ccef318ff1bc99e5dea980111de989/
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> Note: I believe that the -lpthread conditionally added to LIBS when
> static linking is useless now. Indeed, the two C libraries that
> support static linking (musl and uclibc) now have a single libc
> library, so -lpthread is not needed. Glibc does not support static
> linking.
I've applied both patches to master. The cc-tool patch has been merged
upstream already (so I adjusted the patch description). No feedback from
upstream on the boost.m4 patch though.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-08-23 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 13:34 [Buildroot] [PATCH 1/2] cc-tool: pass -latomic in LIBS Thomas Petazzoni
2017-08-20 13:34 ` [Buildroot] [PATCH 2/2] cc-tool: add patch fixing boost.m4 logic for static linking Thomas Petazzoni
2017-08-20 13:54 ` Thomas Petazzoni
2017-08-20 13:54 ` [Buildroot] [PATCH 1/2] cc-tool: pass -latomic in LIBS Thomas Petazzoni
2017-08-23 21:24 ` 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=20170823232437.64b5b82a@windsurf \
--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