From: Rex Ashbaugh <rexa@xeratech.com>
To: buildroot@busybox.net
Subject: [Buildroot] Glibc instead of uclibc
Date: Wed, 5 Mar 2008 10:23:51 -0700 [thread overview]
Message-ID: <6311fe0b0803050923uf9686eep184516ce1bf14b8c@mail.gmail.com> (raw)
In-Reply-To: <c05908680803050916l5077f6f7xfc0e2d3100d60fa8@mail.gmail.com>
yes and yes.
unless you can find a suitable pre-built cross glibc toolchain somewhere
online.
-Rex
On 3/5/08, Salvatore Fassi <salvatore.fassi@gmail.com> wrote:
>
> So is not possible to use the toolchain that is currently installed on my
> linux pc?
> Must I download binutils, gcc etc etc to compile a brand new toolchain
> (following the instructions provided in some cross-compiler how-to)?
>
>
> On Wed, Mar 5, 2008 at 5:59 PM, <sjhill@realitydiluted.com> wrote:
>
> > The only way to use glibc is to build an external glibc toolchain and
> > then specify using an external toolchain in buildroot.
> >
> > -Steve
> >
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080305/347dd65c/attachment-0001.htm
next prev parent reply other threads:[~2008-03-05 17:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 15:44 [Buildroot] Glibc instead of uclibc Salvatore Fassi
2008-03-05 16:59 ` sjhill at realitydiluted.com
2008-03-05 17:16 ` Salvatore Fassi
2008-03-05 17:23 ` JS
2008-03-05 17:33 ` Salvatore Fassi
2008-03-06 7:12 ` Emil Krüper
2008-03-06 7:27 ` Salvatore Fassi
2008-03-06 9:25 ` Salvatore Fassi
2008-03-07 17:18 ` Salvatore Fassi
2008-03-07 18:17 ` sjhill at realitydiluted.com
2008-03-05 17:23 ` Rex Ashbaugh [this message]
2008-03-05 17:27 ` Salvatore Fassi
2008-03-05 17:28 ` sjhill at realitydiluted.com
-- strict thread matches above, loose matches on Subject: below --
2012-08-03 14:47 [Buildroot] glibc " Zoran Djordjevic
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=6311fe0b0803050923uf9686eep184516ce1bf14b8c@mail.gmail.com \
--to=rexa@xeratech.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