From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot with glibc instead of uclibc because i need some libraries not provided for uclibc
Date: Thu, 22 Jan 2009 15:18:27 +0100 [thread overview]
Message-ID: <49788033.3090906@cetrtapot.si> (raw)
In-Reply-To: <COL102-DS17A5B4A2FA03C71DFDBD3DDCCE0@phx.gbl>
Daniel Laird wrote:
> Do you mean 'an external toolchain with glibc' or using buildroot to build a toolchain with glibc?
>
The second, to build a toolchain that uses glibc instead of uClibc.
TIA,
Hinko
--
Hinko Ko?evar, OSS developer
?ETRTA POT, d.o.o.
Planina 3, 4000 Kranj, SI EU
tel ++386 (0) 4 280 66 03
e-mail hinko.kocevar at cetrtapot.si
http www.cetrtapot.si
prev parent reply other threads:[~2009-01-22 14:18 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
2009-01-22 13:33 ` Hinko Kocevar
2009-01-22 14:04 ` Daniel Laird
2009-01-22 14:18 ` Hinko Kocevar [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=49788033.3090906@cetrtapot.si \
--to=hinko.kocevar@cetrtapot.si \
--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