From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] audiofile: needs dynamic library
Date: Tue, 12 Nov 2013 13:17:57 +0100 [thread overview]
Message-ID: <20131112131757.21f166df@skate> (raw)
In-Reply-To: <52821764.5060109@zacarias.com.ar>
Dear Gustavo Zacarias,
On Tue, 12 Nov 2013 08:56:20 -0300, Gustavo Zacarias wrote:
> On 11/12/2013 08:42 AM, Peter Korsgaard wrote:
> > Looking at the build log, the only reason why it fails is that
> > libtool is acting up. It wants to link with libstdc++.so instead of
> > libstdc++.a.
> >
> > A quick test shows that you can fix it by passing -static instead of
> > --static in LDFLAGS, but that effectively reverts 0a4bd19f4a136930c:
> >
> > http://git.buildroot.net/buildroot/commit/?id=0a4bd19f4a136930c
> >
> > Does anybody know what the right solution is?
>
> I think this is related to the nettle failure i've mentioned, after
> the gcc conversion host-gcc-final isn't installing libstdc++.a, and
> after an extra look it isn't even building it because of
> --disable-static in the default CONFIGURE_CMDS.
> So it'll never find a libstdc++.a for the internal toolchain in
> staging. Regards.
I'll try to have a look at this issue tonight.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-12 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 8:28 [Buildroot] [PATCH] audiofile: needs dynamic library spdawson at gmail.com
2013-11-12 11:42 ` Peter Korsgaard
2013-11-12 11:56 ` Gustavo Zacarias
2013-11-12 12:17 ` Thomas Petazzoni [this message]
2013-11-12 12:23 ` Peter Korsgaard
2013-11-12 12:25 ` Gustavo Zacarias
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=20131112131757.21f166df@skate \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.