From: Khem Raj <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFT] Glibc 2.23 and binutils 2.26
Date: Sun, 31 Jan 2016 00:53:39 -0800 [thread overview]
Message-ID: <CAMKF1spuDDiw52Aca1hepV7aWGF_LSmUk2GACLSOPWUsWvy2mw@mail.gmail.com> (raw)
In-Reply-To: <1454229127.27087.11.camel@linuxfoundation.org>
On Sun, Jan 31, 2016 at 12:32 AM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Fri, 2016-01-29 at 06:44 -0800, Khem Raj wrote:
>> On Fri, Jan 29, 2016 at 6:14 AM, Alexander Kanavin
>> <alexander.kanavin@linux.intel.com> wrote:
>> > On 01/17/2016 01:54 PM, Khem Raj wrote:
>> > >
>> > > upstream glibc and binutils release branches have been cut out
>> > > and are
>> > > being made ready for next release
>> > > I have put together update patchset for both of them
>> > >
>> > > here are the branches
>> > >
>> > > https://github.com/kraj/openembedded-core/tree/kraj/binutils-2.26
>> > > https://github.com/kraj/openembedded-core/tree/kraj/glibc-2.23
>> >
>> >
>> > Hello Khem,
>> >
>> > when are you planning to submit these?
>>
>> binutils exposes a problem for ppc as a result kernel fails to build.
>> The fix is to drop
>> http://git.openembedded.org/openembedded-core/tree/meta/recipes-devto
>> ols/gcc/gcc-5.3/0030-Enable-SPE-AltiVec-generation-on-powepc-linux
>> -target.patch
>>
>> that patch makes generic ppc configs to be specific to fsl ppc.
>> but we need context as to why this was done
>>
>> glibc is still not released.
>
> I ran the binutils upgrade in -next on the autobuilder. It looked
> mostly good but with poky-lsb we did see:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/b
> uilds/635/steps/BuildImages/logs/stdio
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/b
> uilds/635/steps/BuildImages_1/logs/stdio
it looks like -fpie is the factor here, I will try to reproduce it here locally
may be we can get away by using system zlib instead of internal one
>
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2016-01-31 8:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 11:54 [RFT] Glibc 2.23 and binutils 2.26 Khem Raj
2016-01-22 1:28 ` [oe] " akuster808
2016-01-22 1:28 ` akuster808
2016-01-27 2:11 ` [oe] " ChenQi
2016-01-27 2:11 ` ChenQi
2016-01-27 5:30 ` [oe] " Khem Raj
2016-01-27 5:30 ` Khem Raj
2016-01-29 14:14 ` Alexander Kanavin
2016-01-29 14:44 ` Khem Raj
2016-01-31 8:32 ` Richard Purdie
2016-01-31 8:53 ` Khem Raj [this message]
2016-02-01 9:12 ` Richard Purdie
2016-02-01 17:02 ` Khem Raj
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=CAMKF1spuDDiw52Aca1hepV7aWGF_LSmUk2GACLSOPWUsWvy2mw@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 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.