From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Explicit dependencies on uclibc in makefiles
Date: Thu, 13 Aug 2009 21:02:02 +0200 [thread overview]
Message-ID: <20090813210202.3340114c@surf> (raw)
In-Reply-To: <d6cda7730908130743ic7fa66fy5f32814fc828d887@mail.gmail.com>
Le Thu, 13 Aug 2009 11:43:27 -0300,
Thiago A. Corr?a <thiago.correa@gmail.com> a ?crit :
> Ah, ok. I never looked it up at the top Makefile. Well, then I guess
> we could drop uclibc from all packages/*
I'll have a closer look at this, but I think yes.
> This actually should be done for the glibc support to work properly I
> guess.
Depends whether you're talking about glibc support in toolchains
generated by Buildroot, or glibc support for external toolchains,
generated with external tools (crosstool-ng, etc.) or downloaded from
third parties (Codesourcery, vendor, etc.). The former is not supported
by Buildroot at this time. The latter is supported, and the
toolchain/external-toolchain/ext-tool.mk implements a uclibc: target,
regardless of whether the C library of the external toolchain is uclibc
or glibc.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-08-13 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 15:55 [Buildroot] Explicit dependencies on uclibc in makefiles Will Newton
2009-08-13 14:05 ` Thiago A. Corrêa
2009-08-13 14:19 ` Will Newton
2009-08-13 14:37 ` Hans-Christian Egtvedt
2009-08-13 14:43 ` Thiago A. Corrêa
2009-08-13 19:02 ` Thomas Petazzoni [this message]
2009-08-20 8:52 ` Bernhard Reutner-Fischer
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=20090813210202.3340114c@surf \
--to=thomas.petazzoni@free-electrons.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