From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] audiofile: does not build with static-only
Date: Sat, 24 May 2014 18:45:41 +0200 [thread overview]
Message-ID: <20140524184541.47d3f8f9@free-electrons.com> (raw)
In-Reply-To: <1400941494-29900-1-git-send-email-luca@lucaceresoli.net>
Dear Luca Ceresoli,
On Sat, 24 May 2014 16:24:54 +0200, Luca Ceresoli wrote:
> Also propagate to its reverse dependency (audiofile module for mpd).
>
> Fixes:
> http://autobuild.buildroot.net/results/327/327c18db4e5d0ddc2c72a4684e103c19a1405e50/
> http://autobuild.buildroot.org/results/c8b/c8b64588eebf0bd8d879881b65e9d8efde00397d/
> http://autobuild.buildroot.org/results/028/028a3b97d56674560b8aa90b6e44b2e91858a5cb/
>
> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
No, I disagree. The real problem is the fact that we pass --static
instead of -static when building statically, so libtool turns -lstdc++
into a full path to libstdc++.so instead of libstdc++.a.
The real fix is to understand why we switched from -static to --static
a few years ago: there is a commit from Andy Kennedy making this
change, but the commit log is quite fuzzy about why this is actually
needed.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-24 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 14:24 [Buildroot] [PATCH] audiofile: does not build with static-only Luca Ceresoli
2014-05-24 16:45 ` Thomas Petazzoni [this message]
2014-05-24 23:13 ` Gustavo Zacarias
2014-05-25 20:39 ` Peter Korsgaard
2014-05-25 21:00 ` Luca Ceresoli
2014-05-25 21:29 ` Gustavo Zacarias
2014-05-28 16:15 ` Arnout Vandecappelle
2014-05-29 7:54 ` Thomas Petazzoni
2014-05-26 9:34 ` Thomas Petazzoni
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=20140524184541.47d3f8f9@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