All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	openembeded-devel <Openembedded-devel@lists.openembedded.org>
Subject: Re: [OE-core] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade
Date: Tue, 17 Feb 2015 18:50:53 +0100	[thread overview]
Message-ID: <CA+chaQdaa+S3AC8YYzmHdv7beMxBzP_03C25Jn=5NiE=DxmGjg@mail.gmail.com> (raw)
In-Reply-To: <1424037551.20217.103.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 2890 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	openembeded-devel <Openembedded-devel@lists.openembedded.org>
Subject: Re: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade
Date: Tue, 17 Feb 2015 18:50:53 +0100	[thread overview]
Message-ID: <CA+chaQdaa+S3AC8YYzmHdv7beMxBzP_03C25Jn=5NiE=DxmGjg@mail.gmail.com> (raw)
In-Reply-To: <1424037551.20217.103.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 2890 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	openembeded-devel <Openembedded-devel@lists.openembedded.org>
Subject: Re: [OE-core] [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade
Date: Tue, 17 Feb 2015 18:50:53 +0100	[thread overview]
Message-ID: <CA+chaQdaa+S3AC8YYzmHdv7beMxBzP_03C25Jn=5NiE=DxmGjg@mail.gmail.com> (raw)
In-Reply-To: <1424037551.20217.103.camel@linuxfoundation.org>

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
>


  reply	other threads:[~2015-02-17 17:50 UTC|newest]

Thread overview: 109+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 10:02 [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade Khem Raj
2015-02-02 10:40 ` Burton, Ross
2015-02-02 10:40   ` [yocto] " Burton, Ross
2015-02-02 10:40   ` Burton, Ross
2015-02-02 10:53   ` Khem Raj
2015-02-02 10:53     ` [yocto] " Khem Raj
2015-02-02 10:54   ` Khem Raj
2015-02-02 10:54     ` [yocto] " Khem Raj
2015-02-02 17:25     ` Burton, Ross
2015-02-02 17:25       ` [yocto] " Burton, Ross
2015-02-02 17:25       ` Burton, Ross
2015-02-02 17:40       ` Khem Raj
2015-02-02 17:40         ` [yocto] " Khem Raj
2015-02-02 17:40         ` Khem Raj
2015-02-02 17:50         ` Burton, Ross
2015-02-02 17:50           ` [yocto] " Burton, Ross
2015-02-02 17:50           ` Burton, Ross
2015-02-02 18:33           ` Khem Raj
2015-02-02 18:33             ` [yocto] " Khem Raj
2015-02-02 18:33             ` Khem Raj
2015-02-02 21:45             ` Burton, Ross
2015-02-02 21:45               ` [yocto] " Burton, Ross
2015-02-02 21:45               ` Burton, Ross
2015-02-03  5:03               ` Khem Raj
2015-02-03  5:03                 ` [yocto] " Khem Raj
2015-02-03 11:55                 ` Burton, Ross
2015-02-03 11:55                   ` [yocto] " Burton, Ross
2015-02-03 11:55                   ` Burton, Ross
2015-02-03 14:43                 ` Dan McGregor
2015-02-03 14:43                   ` [OE-core] " Dan McGregor
2015-02-12  7:35                   ` [OE-core] " Khem Raj
2015-02-12  7:35                     ` [OE-core] [yocto] " Khem Raj
2015-02-12  7:35                     ` Khem Raj
2015-02-14  7:53                     ` [OE-core] " Burton, Ross
2015-02-14  7:53                       ` [OE-core] [yocto] " Burton, Ross
2015-02-14  7:53                       ` Burton, Ross
2015-02-14 10:06                     ` [OE-core] " Richard Purdie
2015-02-14 10:06                       ` [OE-core] [yocto] " Richard Purdie
2015-02-14 10:06                       ` Richard Purdie
2015-02-14 13:08                       ` [OE-core] " Burton, Ross
2015-02-14 13:08                         ` [OE-core] [yocto] " Burton, Ross
2015-02-14 13:08                         ` Burton, Ross
2015-02-14 15:15                         ` Dan McGregor
2015-02-14 15:15                           ` [OE-core] " Dan McGregor
2015-02-15 21:59                       ` [OE-core] " Richard Purdie
2015-02-15 21:59                         ` [OE-core] [yocto] " Richard Purdie
2015-02-15 21:59                         ` Richard Purdie
2015-02-17 17:50                         ` Martin Jansa [this message]
2015-02-17 17:50                           ` [OE-core] " Martin Jansa
2015-02-17 17:50                           ` Martin Jansa
2015-02-17 19:02                           ` [PATCH 1/2] valgrind: add glibc-2.21 to glibc.patch Martin Jansa
2015-02-17 19:02                             ` [PATCH 2/2] license.bbclass: fix unexpected operator for LICENSE values with space Martin Jansa
2015-02-18  7:15                       ` [OE-core] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade Khem Raj
2015-02-18  7:15                         ` [OE-core] [yocto] " Khem Raj
2015-02-18  7:15                         ` Khem Raj
2015-02-18  7:46                         ` [OE-core] " Richard Purdie
2015-02-18  7:46                           ` [OE-core] [yocto] " Richard Purdie
2015-02-18  7:46                           ` Richard Purdie
2015-02-18  9:01                           ` [OE-core] " Khem Raj
2015-02-18  9:01                             ` [OE-core] [yocto] " Khem Raj
2015-02-18  9:01                             ` Khem Raj
2015-02-18 11:51                             ` [OE-core] " Richard Purdie
2015-02-18 11:51                               ` [OE-core] [yocto] " Richard Purdie
2015-02-18 11:51                               ` Richard Purdie
2015-02-18 13:06                               ` [OE-core] " Richard Purdie
2015-02-18 13:06                                 ` [yocto] " Richard Purdie
2015-02-18 13:06                                 ` [yocto] " Richard Purdie
2015-02-18 18:38                                 ` [OE-core] " Khem Raj
2015-02-18 18:38                                   ` [yocto] " Khem Raj
2015-02-18 18:38                                   ` [yocto] " Khem Raj
2015-02-18 21:41                                   ` [OE-core] " Richard Purdie
2015-02-18 21:41                                     ` [yocto] " Richard Purdie
2015-02-18 21:41                                     ` [yocto] " Richard Purdie
2015-02-19  0:23                                     ` [OE-core] " Khem Raj
2015-02-19  0:23                                       ` [yocto] " Khem Raj
2015-02-19  0:23                                       ` [yocto] " Khem Raj
2015-02-19  0:28                                       ` [OE-core] " Khem Raj
2015-02-19  0:28                                         ` [yocto] " Khem Raj
2015-02-19  0:28                                         ` [yocto] " Khem Raj
2015-02-19  0:31                                         ` [OE-core] " Khem Raj
2015-02-19  0:31                                           ` [yocto] " Khem Raj
2015-02-19  0:31                                           ` [yocto] " Khem Raj
2015-02-19  3:36                                           ` [OE-core] " Khem Raj
2015-02-19  3:36                                             ` [yocto] " Khem Raj
2015-02-19  3:36                                             ` [yocto] " Khem Raj
2015-02-02 16:41 ` akuster
2015-02-02 17:26   ` Burton, Ross
2015-02-02 17:26     ` [yocto] " Burton, Ross
2015-02-02 17:26     ` Burton, Ross
2015-02-02 17:43     ` Khem Raj
2015-02-02 17:43       ` [yocto] " Khem Raj
2015-02-02 17:43       ` Khem Raj
2015-02-20 18:03 ` Richard Purdie
2015-02-20 18:03   ` [yocto] " Richard Purdie
2015-02-21  0:27   ` [OE-core] " Peter Urbanec
2015-02-21  0:27     ` [OE-core] [yocto] " Peter Urbanec
2015-02-21  0:27     ` Peter Urbanec
2015-02-24  6:34     ` [OE-core] " Khem Raj
2015-02-24  6:34       ` [OE-core] [yocto] " Khem Raj
2015-02-24  6:34       ` Khem Raj
2015-02-21  9:22   ` [OE-core] " Richard Purdie
2015-02-21  9:22     ` [OE-core] [yocto] " Richard Purdie
2015-02-21  9:22     ` Richard Purdie
2015-02-24  6:59     ` [OE-core] " Khem Raj
2015-02-24  6:59       ` [OE-core] [yocto] " Khem Raj
2015-02-24  6:59       ` Khem Raj
2015-02-24 21:58       ` [OE-core] " Khem Raj
2015-02-24 21:58         ` [OE-core] [yocto] " Khem Raj
2015-02-24 21:58         ` 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='CA+chaQdaa+S3AC8YYzmHdv7beMxBzP_03C25Jn=5NiE=DxmGjg@mail.gmail.com' \
    --to=martin.jansa@gmail.com \
    --cc=Openembedded-devel@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=yocto@yoctoproject.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.