From: sjhill at realitydiluted.com <sjhill@realitydiluted.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot with glibc instead of uclibc because i need some libraries not provided for uclibc
Date: Wed, 21 Jan 2009 08:54:18 -0600 [thread overview]
Message-ID: <20090121145418.GA10568@real.realitydiluted.com> (raw)
In-Reply-To: <87k58osp9t.fsf@macbook.be.48ers.dk>
> No such thing exists. You should in theory be able to do it with the
> external toolchain support, but I've never heard from anyone trying
> it.
>
I was the one who originally put external toolchain support into buildroot
specifically to use glibc instead of uClibc via an external toolchain.
That said, buildroot does not support building glibc or a glibc toolchain
within the buildroot framework.
-Steve
next prev parent reply other threads:[~2009-01-21 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 14:27 [Buildroot] buildroot with glibc instead of uclibc because i need some libraries not provided for uclibc Alessio.Stella at gidi.it
2009-01-21 14:32 ` Peter Korsgaard
2009-01-21 14:54 ` sjhill at realitydiluted.com [this message]
2009-01-22 13:33 ` Hinko Kocevar
2009-01-22 14:04 ` Daniel Laird
2009-01-22 14:18 ` Hinko Kocevar
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=20090121145418.GA10568@real.realitydiluted.com \
--to=sjhill@realitydiluted.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