From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 77BE8E0077E; Tue, 17 Feb 2015 09:50:59 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (martin.jansa[at]gmail.com) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.212.173 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B2D95E00757 for ; Tue, 17 Feb 2015 09:50:55 -0800 (PST) Received: by mail-wi0-f173.google.com with SMTP id bs8so35619221wib.0 for ; Tue, 17 Feb 2015 09:50:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=F4S9cBwLNgF8NsqFx5oqR2kr90y0krIGVHdWO/hFbSQ=; b=WU4tgZXZoTsaMT/p6JjvLJlymozS1AkvDokI16lksHxAjQLJ4nlFoJRaIQHy4hoQWx Nzxq8Lc8NqVlS509rEFKhz0vWN0Qs2+TT/hUlYWnqbRcdRG9lTyEPSHsH5MXjlL+AyaD RGXN7lRkGHeOn9f1YZp8nFbXyeajzMP1YVt0vuzwgQsE9ruB1LvqBQ6Trw8Ghu1x08t2 tmZ9cIgCPG147vo1GSdWRSAPmhzzZPYDQXRyLX9Q0eeF3Mt2Vv4vjp5GuZvp779FKdbd aCYn+RjiZVlGtQKXmbCgzQwirQGy+9jB8k2tmTzeHMAIJlM2jrGirfUfrmxVEcX50i9M 8LwQ== MIME-Version: 1.0 X-Received: by 10.194.5.37 with SMTP id p5mr64759179wjp.20.1424195454008; Tue, 17 Feb 2015 09:50:54 -0800 (PST) Received: by 10.194.85.225 with HTTP; Tue, 17 Feb 2015 09:50:53 -0800 (PST) In-Reply-To: <1424037551.20217.103.camel@linuxfoundation.org> References: <80920FD0-CA08-45D7-9A41-3971FB2D58D7@gmail.com> <1423908404.20217.100.camel@linuxfoundation.org> <1424037551.20217.103.camel@linuxfoundation.org> Date: Tue, 17 Feb 2015 18:50:53 +0100 Message-ID: From: Martin Jansa To: Richard Purdie Cc: "yocto@yoctoproject.org" , Patches and discussions about the oe-core layer , openembeded-devel Subject: Re: [OE-core] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2015 17:50:59 -0000 Content-Type: multipart/alternative; boundary=047d7b5d5736208318050f4c58de --047d7b5d5736208318050f4c58de Content-Type: text/plain; charset=UTF-8 We should extend: ./meta/recipes-devtools/valgrind/valgrind/glibc-2.20.patch to allow building valgrind with glibc-2.21, currently it fails with: | checking the GLIBC_VERSION version... unsupported version 2.21 | configure: error: Valgrind requires glibc version 2.2 - 2.19 | Configure failed. The contents of all config.log files follows to aid debugging | ERROR: oe_runconf failed On Sun, Feb 15, 2015 at 10:59 PM, Richard Purdie < richard.purdie@linuxfoundation.org> wrote: > On Sat, 2015-02-14 at 10:06 +0000, Richard Purdie wrote: > > Hi Khem, > > > > On Thu, 2015-02-12 at 15:35 +0800, Khem Raj wrote: > > > I have refreshed the branch to include the patch which moves the src > > > uri to use the newly released glibc 2.21 branch > > > and please run it via autobuilder ( top 5 commits ) > > > > Its running on the autobuilder at the moment. Errors will be reported to > > the error reporting system and can be seen at: > > > > > http://errors.yoctoproject.org/Errors/Search/?items=10&query=be29d13a847d458efaf542ed302e48050f67a655 > > > > Right now, poky-tiny failed due to warning are errors and unused > > symbols. Minnow failed due to SSE instruction issues. Full build logs > > are also available on the autobuilder: > > > > https://autobuilder.yoctoproject.org/main/tgrid > > > > as ross/mut-next. We do have other changes in the branch but the above > > are pretty clearly glibc. > > > > Other errors will go to the places above as the builds complete/fail. > > FWIW I tested the gcc upgrade without glibc and that seems ok so I've > merged that whilst we work out the issues with glibc. > > Cheers, > > Richard > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > --047d7b5d5736208318050f4c58de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
We should extend:
./meta/recipes-devtools/valgri= nd/valgrind/glibc-2.20.patch

to allow building valgr= ind with glibc-2.21, currently it fails with:

| checking the GLIBC_VERSION version... unsupported version 2.21
| configure: error: Valgrind requires glibc version 2.2 - 2.19
|= Configure failed. The contents of all config.log files follows to aid debu= gging
| ERROR: oe_runconf failed

=

On Sun, Feb 15, 2= 015 at 10:59 PM, Richard Purdie <richard.purdie@linuxfoun= dation.org> wrote:
On Sat, 2015-02-14 at 10:06 +0000, Richard Purdie wrote:
> Hi Khem,
>
> On Thu, 2015-02-12 at 15:35 +0800, Khem Raj wrote:
> > I have refreshed the branch to include the patch which moves the = src
> > uri to use the newly released glibc 2.21 branch
> > and please run it via autobuilder ( top 5 commits )
>
> Its running on the autobuilder at the moment. Errors will be reported = to
> the error reporting system and can be seen at:
>
> http:= //errors.yoctoproject.org/Errors/Search/?items=3D10&query=3Dbe29d13a847= d458efaf542ed302e48050f67a655
>
> Right now, poky-tiny failed due to warning are errors and unused
> symbols. Minnow failed due to SSE instruction issues. Full build logs<= br> > are also available on the autobuilder:
>
> https://autobuilder.yoctoproject.org/main/tgrid
>
> as ross/mut-next. We do have other changes in the branch but the above=
> are pretty clearly glibc.
>
> Other errors will go to the places above as the builds complete/fail.<= br>
FWIW I tested the gcc upgrade without glibc and that seems ok so I&#= 39;ve
merged that whilst we work out the issues with glibc.

Cheers,

Richard

--
_______________________________________________
Openembedded-core mailing list
Openembedded-co= re@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembe= dded-core

--047d7b5d5736208318050f4c58de-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by mail.openembedded.org (Postfix) with ESMTP id C0108606E8; Tue, 17 Feb 2015 17:50:53 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id hi2so35834839wib.0; Tue, 17 Feb 2015 09:50:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=F4S9cBwLNgF8NsqFx5oqR2kr90y0krIGVHdWO/hFbSQ=; b=WU4tgZXZoTsaMT/p6JjvLJlymozS1AkvDokI16lksHxAjQLJ4nlFoJRaIQHy4hoQWx Nzxq8Lc8NqVlS509rEFKhz0vWN0Qs2+TT/hUlYWnqbRcdRG9lTyEPSHsH5MXjlL+AyaD RGXN7lRkGHeOn9f1YZp8nFbXyeajzMP1YVt0vuzwgQsE9ruB1LvqBQ6Trw8Ghu1x08t2 tmZ9cIgCPG147vo1GSdWRSAPmhzzZPYDQXRyLX9Q0eeF3Mt2Vv4vjp5GuZvp779FKdbd aCYn+RjiZVlGtQKXmbCgzQwirQGy+9jB8k2tmTzeHMAIJlM2jrGirfUfrmxVEcX50i9M 8LwQ== MIME-Version: 1.0 X-Received: by 10.194.5.37 with SMTP id p5mr64759179wjp.20.1424195454008; Tue, 17 Feb 2015 09:50:54 -0800 (PST) Received: by 10.194.85.225 with HTTP; Tue, 17 Feb 2015 09:50:53 -0800 (PST) In-Reply-To: <1424037551.20217.103.camel@linuxfoundation.org> References: <80920FD0-CA08-45D7-9A41-3971FB2D58D7@gmail.com> <1423908404.20217.100.camel@linuxfoundation.org> <1424037551.20217.103.camel@linuxfoundation.org> Date: Tue, 17 Feb 2015 18:50:53 +0100 Message-ID: From: Martin Jansa To: Richard Purdie Cc: "yocto@yoctoproject.org" , Patches and discussions about the oe-core layer , openembeded-devel Subject: Re: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2015 17:50:57 -0000 Content-Type: multipart/alternative; boundary=047d7b5d5736208318050f4c58de --047d7b5d5736208318050f4c58de Content-Type: text/plain; charset=UTF-8 We should extend: ./meta/recipes-devtools/valgrind/valgrind/glibc-2.20.patch to allow building valgrind with glibc-2.21, currently it fails with: | checking the GLIBC_VERSION version... unsupported version 2.21 | configure: error: Valgrind requires glibc version 2.2 - 2.19 | Configure failed. The contents of all config.log files follows to aid debugging | ERROR: oe_runconf failed On Sun, Feb 15, 2015 at 10:59 PM, Richard Purdie < richard.purdie@linuxfoundation.org> wrote: > On Sat, 2015-02-14 at 10:06 +0000, Richard Purdie wrote: > > Hi Khem, > > > > On Thu, 2015-02-12 at 15:35 +0800, Khem Raj wrote: > > > I have refreshed the branch to include the patch which moves the src > > > uri to use the newly released glibc 2.21 branch > > > and please run it via autobuilder ( top 5 commits ) > > > > Its running on the autobuilder at the moment. Errors will be reported to > > the error reporting system and can be seen at: > > > > > http://errors.yoctoproject.org/Errors/Search/?items=10&query=be29d13a847d458efaf542ed302e48050f67a655 > > > > Right now, poky-tiny failed due to warning are errors and unused > > symbols. Minnow failed due to SSE instruction issues. Full build logs > > are also available on the autobuilder: > > > > https://autobuilder.yoctoproject.org/main/tgrid > > > > as ross/mut-next. We do have other changes in the branch but the above > > are pretty clearly glibc. > > > > Other errors will go to the places above as the builds complete/fail. > > FWIW I tested the gcc upgrade without glibc and that seems ok so I've > merged that whilst we work out the issues with glibc. > > Cheers, > > Richard > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > --047d7b5d5736208318050f4c58de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
We should extend:
./meta/recipes-devtools/valgri= nd/valgrind/glibc-2.20.patch

to allow building valgr= ind with glibc-2.21, currently it fails with:

| checking the GLIBC_VERSION version... unsupported version 2.21
| configure: error: Valgrind requires glibc version 2.2 - 2.19
|= Configure failed. The contents of all config.log files follows to aid debu= gging
| ERROR: oe_runconf failed

=

On Sun, Feb 15, 2= 015 at 10:59 PM, Richard Purdie <richard.purdie@linuxfoun= dation.org> wrote:
On Sat, 2015-02-14 at 10:06 +0000, Richard Purdie wrote:
> Hi Khem,
>
> On Thu, 2015-02-12 at 15:35 +0800, Khem Raj wrote:
> > I have refreshed the branch to include the patch which moves the = src
> > uri to use the newly released glibc 2.21 branch
> > and please run it via autobuilder ( top 5 commits )
>
> Its running on the autobuilder at the moment. Errors will be reported = to
> the error reporting system and can be seen at:
>
> http:= //errors.yoctoproject.org/Errors/Search/?items=3D10&query=3Dbe29d13a847= d458efaf542ed302e48050f67a655
>
> Right now, poky-tiny failed due to warning are errors and unused
> symbols. Minnow failed due to SSE instruction issues. Full build logs<= br> > are also available on the autobuilder:
>
> https://autobuilder.yoctoproject.org/main/tgrid
>
> as ross/mut-next. We do have other changes in the branch but the above=
> are pretty clearly glibc.
>
> Other errors will go to the places above as the builds complete/fail.<= br>
FWIW I tested the gcc upgrade without glibc and that seems ok so I&#= 39;ve
merged that whilst we work out the issues with glibc.

Cheers,

Richard

--
_______________________________________________
Openembedded-core mailing list
Openembedded-co= re@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembe= dded-core

--047d7b5d5736208318050f4c58de-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by mail.openembedded.org (Postfix) with ESMTP id C0108606E8; Tue, 17 Feb 2015 17:50:53 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id hi2so35834839wib.0; Tue, 17 Feb 2015 09:50:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=F4S9cBwLNgF8NsqFx5oqR2kr90y0krIGVHdWO/hFbSQ=; b=WU4tgZXZoTsaMT/p6JjvLJlymozS1AkvDokI16lksHxAjQLJ4nlFoJRaIQHy4hoQWx Nzxq8Lc8NqVlS509rEFKhz0vWN0Qs2+TT/hUlYWnqbRcdRG9lTyEPSHsH5MXjlL+AyaD RGXN7lRkGHeOn9f1YZp8nFbXyeajzMP1YVt0vuzwgQsE9ruB1LvqBQ6Trw8Ghu1x08t2 tmZ9cIgCPG147vo1GSdWRSAPmhzzZPYDQXRyLX9Q0eeF3Mt2Vv4vjp5GuZvp779FKdbd aCYn+RjiZVlGtQKXmbCgzQwirQGy+9jB8k2tmTzeHMAIJlM2jrGirfUfrmxVEcX50i9M 8LwQ== MIME-Version: 1.0 X-Received: by 10.194.5.37 with SMTP id p5mr64759179wjp.20.1424195454008; Tue, 17 Feb 2015 09:50:54 -0800 (PST) Received: by 10.194.85.225 with HTTP; Tue, 17 Feb 2015 09:50:53 -0800 (PST) In-Reply-To: <1424037551.20217.103.camel@linuxfoundation.org> References: <80920FD0-CA08-45D7-9A41-3971FB2D58D7@gmail.com> <1423908404.20217.100.camel@linuxfoundation.org> <1424037551.20217.103.camel@linuxfoundation.org> Date: Tue, 17 Feb 2015 18:50:53 +0100 Message-ID: From: Martin Jansa To: Richard Purdie X-Content-Filtered-By: Mailman/MimeDel 2.1.12 Cc: "yocto@yoctoproject.org" , Patches and discussions about the oe-core layer , openembeded-devel Subject: Re: [OE-core] [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2015 17:50:57 -0000 Content-Type: text/plain; charset=UTF-8 We should extend: ./meta/recipes-devtools/valgrind/valgrind/glibc-2.20.patch to allow building valgrind with glibc-2.21, currently it fails with: | checking the GLIBC_VERSION version... unsupported version 2.21 | configure: error: Valgrind requires glibc version 2.2 - 2.19 | Configure failed. The contents of all config.log files follows to aid debugging | ERROR: oe_runconf failed On Sun, Feb 15, 2015 at 10:59 PM, Richard Purdie < richard.purdie@linuxfoundation.org> wrote: > On Sat, 2015-02-14 at 10:06 +0000, Richard Purdie wrote: > > Hi Khem, > > > > On Thu, 2015-02-12 at 15:35 +0800, Khem Raj wrote: > > > I have refreshed the branch to include the patch which moves the src > > > uri to use the newly released glibc 2.21 branch > > > and please run it via autobuilder ( top 5 commits ) > > > > Its running on the autobuilder at the moment. Errors will be reported to > > the error reporting system and can be seen at: > > > > > http://errors.yoctoproject.org/Errors/Search/?items=10&query=be29d13a847d458efaf542ed302e48050f67a655 > > > > Right now, poky-tiny failed due to warning are errors and unused > > symbols. Minnow failed due to SSE instruction issues. Full build logs > > are also available on the autobuilder: > > > > https://autobuilder.yoctoproject.org/main/tgrid > > > > as ross/mut-next. We do have other changes in the branch but the above > > are pretty clearly glibc. > > > > Other errors will go to the places above as the builds complete/fail. > > FWIW I tested the gcc upgrade without glibc and that seems ok so I've > merged that whilst we work out the issues with glibc. > > Cheers, > > Richard > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core >