From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Compile static versions of gcc libraries
Date: Mon, 14 Oct 2013 11:27:41 +0200 [thread overview]
Message-ID: <20131014112741.279b7c49@skate> (raw)
In-Reply-To: <2096076.neUu8LQVqN@sagittae>
Dear J?r?me Pouiller,
On Mon, 14 Oct 2013 11:16:08 +0200, J?r?me Pouiller wrote:
> On Sunday 13 October 2013 15:33:55 Thomas Petazzoni wrote:
> > Dear J?r?me Pouiller,
> >
> > On Thu, 10 Oct 2013 11:40:42 +0200, J?r?me Pouiller wrote:
> > > Since default configure options for host packages include
> > > --disable-static, gcc was not configured to build static version of
> > > its libraries (libgcc.a, libstdc++.a, ...).
> >
> > I'm a bit confused, the toolchains I have here definitely do have
> > libgcc.a :
> >
> > $ find . -name 'libgcc.a'
> > ./host/usr/lib/gcc/sh4-buildroot-linux-uclibc/4.7.3/libgcc.a
>
> Sorry, in contrary of what I wrote in my commit message, this does not
> impact libgcc.a. However, it impacts libstdc++.a, libgomp.a,
> libmudflap*.a, ...
>
> > What practical issue are you seeing?
> My main concern is libstdc++.a.
Ah, ok. I'll retry then and see what happens :)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-14 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 9:40 [Buildroot] [PATCH] Compile static versions of gcc libraries Jérôme Pouiller
2013-10-11 21:23 ` Thomas Petazzoni
2013-10-12 6:58 ` Jérôme Pouiller
2013-10-13 13:33 ` Thomas Petazzoni
2013-10-14 9:16 ` Jérôme Pouiller
2013-10-14 9:27 ` Thomas Petazzoni [this message]
2014-01-03 11:55 ` [Buildroot] " Baruch Siach
2014-01-11 22:47 ` [Buildroot] [PATCH] " Peter Korsgaard
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=20131014112741.279b7c49@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.