From: Bryan Hundven <bryanhundven@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org
Subject: Re: [PATCH 2 of 3] Add updated eglibc 2.15
Date: Fri, 02 Mar 2012 01:30:00 -0000 [thread overview]
Message-ID: <CAJ+oik29LxNZjoAuTeYNb3MEa97EYTFX2tKwzKFuQc-=m3LLgQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ+oik17xU-itjn-GbauFAVkq5N6r2oNL049MtZi4B4voGwo7A@mail.gmail.com>
On Thu, Mar 1, 2012 at 5:05 PM, Bryan Hundven <bryanhundven@gmail.com> wrote:
> On Thu, Mar 1, 2012 at 3:41 PM, Bryan Hundven <bryanhundven@gmail.com> wrote:
>> # HG changeset patch
>> # User "Bryan Hundven" <bryanhundven@gmail.com>
>> # Date 1330644229 28800
>> # Node ID 85ff80f395067f7b07dd2558f9c8a7357f18cbf9
>> # Parent cc5c8bd6c1a2cce7d4c009ef9a6f0895fa089699
>> Add updated eglibc 2.15
>>
>> Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
>>
>> diff -r cc5c8bd6c1a2 -r 85ff80f39506 config/libc/eglibc.in
>> --- a/config/libc/eglibc.in Thu Mar 01 15:20:09 2012 -0800
>> +++ b/config/libc/eglibc.in Thu Mar 01 15:23:49 2012 -0800
>> @@ -18,6 +18,12 @@
>> # Don't remove next line
>> # CT_INSERT_VERSION_BELOW
>>
>> +config LIBC_EGLIBC_V_2_15
>> + bool
>> + prompt "2_15"
>> + depends on EXPERIMENTAL
>> + select LIBC_EGLIBC_2_15_or_later
>> +
>> config LIBC_EGLIBC_V_2_14
>> bool
>> prompt "2_14"
>> @@ -83,6 +89,7 @@
>> string
>> # Don't remove next line
>> # CT_INSERT_VERSION_STRING_BELOW
>> + default "2_15" if LIBC_EGLIBC_V_2_15
>> default "2_14" if LIBC_EGLIBC_V_2_14
>> default "2_13" if LIBC_EGLIBC_V_2_13
>> default "2_12" if LIBC_EGLIBC_V_2_12
>> @@ -95,6 +102,10 @@
>> default "2_5" if LIBC_EGLIBC_V_2_5
>> default "trunk" if LIBC_EGLIBC_V_TRUNK
>>
>> +config LIBC_EGLIBC_2_15_or_later
>> + bool
>> + select LIBC_EGLIBC_2_14_or_later
>> +
>> config LIBC_EGLIBC_2_14_or_later
>> bool
>> select LIBC_EGLIBC_2_13_or_later
>
>
> Hmm, the eglibc-2_15 branch seems to have some problems.
> I found some patches to fix the problems I have here:
> http://www.trustanywhere.com/download/public/openwrt/source/tmp/2.15/
>
> Specifically: 300-builtin-expect-needed.patch
>
> The zic and thumb patches might also be helpful, but I don't know if
> we need 200-add-dl-search-paths.patch.
>
> -Bryan
http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=3857022a761ea7251f8e5c0e45d382ebc3e34cf9
This actually seems to be the right patch to backport. I'll test this
in a little bit after my 2_14 build is done.
-Bryan
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2012-03-02 1:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 23:41 [PATCH 0 of 3] Update gcc, eglibc, and kernel versions Bryan Hundven
2012-03-01 23:41 ` [PATCH 2 of 3] Add updated eglibc 2.15 Bryan Hundven
2012-03-02 1:05 ` Bryan Hundven
2012-03-02 1:30 ` Bryan Hundven [this message]
2012-03-26 10:04 ` Florian Fainelli
2012-03-01 23:41 ` [PATCH 3 of 3] Add updated kernel versions: 3.2.7 and 3.2.8 Bryan Hundven
2012-03-01 23:41 ` [PATCH 1 of 3] Add updated gcc 4.6.3 Bryan Hundven
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='CAJ+oik29LxNZjoAuTeYNb3MEa97EYTFX2tKwzKFuQc-=m3LLgQ@mail.gmail.com' \
--to=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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).