From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: deprecate BR2_GCC_SHARED_LIBGCC
Date: Thu, 20 Sep 2012 01:38:36 +0200 [thread overview]
Message-ID: <505A577C.1080700@mind.be> (raw)
I've been playing around a bit with the options of the buildroot toolchain,
and disabled BR2_GCC_SHARED_LIBGCC. Turns out that this makes it impossible
to build shared C++ libraries, because they have to be linked with a shared
libstdc++.so... Also, it looks like libgcc_s.so is still built, but it isn't
copied to the target directory. So there's a risk that something links against
it and fails to run.
So I propose to remove the BR2_GCC_SHARED_LIBGCC option, and instead make it
equal to !BR2_PREFER_STATIC. That will probably still cause problems in some
corner cases, but we reduce the room for error.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
reply other threads:[~2012-09-19 23:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=505A577C.1080700@mind.be \
--to=arnout@mind.be \
--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