From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot-2012.08: Error when selecting crosstool-ng
Date: Tue, 2 Oct 2012 02:09:51 +0200 [thread overview]
Message-ID: <20121002000951.GA4689@tarshish> (raw)
In-Reply-To: <CABRndgy4WMyjqrod4L_N89VRbVD_jKDYpThAMfwNqhdySNrFZQ@mail.gmail.com>
Hi Zvi,
On Tue, Oct 02, 2012 at 01:25:11AM +0200, Zvi Vered wrote:
> I'm using buildroot-2012.08 to create toolchain + file system for an x86
> target.
>
> When I set toolchain to: buildroot, the build was OK.
>
> Then I changed to: crosstool-ng and got the following error:
Questions related to crosstool-ng should go to the crossgcc mailing list. See
under "Contacts" at http://crosstool-ng.org/.
[snip]
> The reason I changed to crosstool-ng is that I want to use glibc and not
> ulibc.
>
> Attached the .config I'm using.
You say you want glibc toolchain, but your .config indicates otherwise:
BR2_TOOLCHAIN_CTNG_uClibc=y
# BR2_TOOLCHAIN_CTNG_eglibc is not set
# BR2_TOOLCHAIN_CTNG_glibc is not set
> Can you help ?
An alternative to building a toolchain from scratch is to use a pre-built
toolchain as external toolchain. Buildroot can even download and install the
Sourcery CodeBench toolchain for you. Just select "External toolchain" in
Toolchain -> Toolchain type, and then select from the options in the
"Toolchain" choice menu.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2012-10-02 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 23:25 [Buildroot] buildroot-2012.08: Error when selecting crosstool-ng Zvi Vered
2012-10-02 0:09 ` Baruch Siach [this message]
[not found] ` <CABRndgz+297jXwaBiThqrhztj-0uUajQu7OY=nRoz7DLxLid8Q@mail.gmail.com>
2012-10-02 14:01 ` Baruch Siach
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=20121002000951.GA4689@tarshish \
--to=baruch@tkos.co.il \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.