From: Kevin Chadwick <ma1l1ists@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Generating external toolchains with Buildroot
Date: Tue, 28 Aug 2012 11:30:47 +0100 [thread overview]
Message-ID: <638833.90681.bm@smtp145.mail.ukl.yahoo.com> (raw)
In-Reply-To: <20120825113012.44b2612f@skate>
> For the toolchains that I've put online at
> http://autobuild.buildroot.org/toolchains/tarballs/, I've solved this
> problem by modifying Buildroot so that it builds mpfr, gmp and mpc as
> static libraries, so that the gcc binaries do not depend to any shared
> libraries besides the C library. And this seems to work fine, though it
> is not a completely satisfying solution.
What's the draw back there?
--
_______________________________________________________________________
'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
universal interface'
(Doug McIlroy)
_______________________________________________________________________
prev parent reply other threads:[~2012-08-28 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-25 9:30 [Buildroot] Generating external toolchains with Buildroot Thomas Petazzoni
2012-08-28 7:36 ` Arnout Vandecappelle
2012-08-28 12:12 ` Thomas Petazzoni
2012-08-28 10:30 ` Kevin Chadwick [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=638833.90681.bm@smtp145.mail.ukl.yahoo.com \
--to=ma1l1ists@yahoo.co.uk \
--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