From: Sebastian Holmqvist <sebastian.holmqvist@gmail.com>
To: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Enable Glibc 2.5
Date: Mon, 08 Apr 2013 21:55:00 -0000 [thread overview]
Message-ID: <E6B5D01E-D5BC-4FF3-936C-D52DCEA60574@gmail.com> (raw)
In-Reply-To: <CAMKF1sq7kRTrMNNMjkx_64ev4cogvq0HkyZYVW9Hk2Rw8RjAuw@mail.gmail.com>
It appears 1.17 supports Glibc 2.5. Thanks for the tip.
--
Sebastian Holmqvist
On 8 apr 2013, at 00:39, Khem Raj <raj.khem@gmail.com> wrote:
> On Sun, Apr 7, 2013 at 2:36 PM, Sebastian Holmqvist
> <sebastian.holmqvist@gmail.com> wrote:
>>
>> Would it be possible to build a toolchain with Glibc 2.5? Menuconfig suggests otherwise.
>
>
>
> 2.5 is quite old. choose an older release of ct-ng which supported it. may be
> http://crosstool-ng.org/download/crosstool-ng/crosstool-ng-0.0.1.tar.bz2
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2013-04-08 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <91C6E43F-B889-4543-BE7C-5ADE87520A3F@gmail.com>
2013-04-07 21:37 ` Sebastian Holmqvist
2013-04-07 22:39 ` Khem Raj
2013-04-08 21:55 ` Sebastian Holmqvist [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=E6B5D01E-D5BC-4FF3-936C-D52DCEA60574@gmail.com \
--to=sebastian.holmqvist@gmail.com \
--cc=crossgcc@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).