* Re: [OE-core] [PATCH 0/3] mesa upgrade
[not found] <cover.1399993010.git.valentin.popa@intel.com>
@ 2014-05-13 15:28 ` Burton, Ross
2014-05-14 20:34 ` Otavio Salvador
2014-06-04 12:52 ` Martin Jansa
0 siblings, 2 replies; 6+ messages in thread
From: Burton, Ross @ 2014-05-13 15:28 UTC (permalink / raw)
To: OE-core, OE-devel
Hi all,
As this is a major release of Mesa I'm expecting breakage somewhere...
Can BSP maintainers please test these patches if their machines build
Mesa? I'm expecting machines that use mesa-gl to break if they don't
just use the pure software drivers (so that's at least EMGD and if I
recall correctly some ARM drivers).
Ross
On 13 May 2014 15:59, Valentin Popa <valentin.popa@intel.com> wrote:
> mesa upgrade to 10.1.3
>
> The following changes since commit 40551859671a1c9da26cfdcda34da952c66ac8c2:
>
> qemu/local.conf.sample: Add sdl PACKAGECONFIG (2014-05-13 08:02:04 +0100)
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib vpopa/mesa
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=vpopa/mesa
>
> Valentin Popa (3):
> dri3proto: add it to oe-core
> libxshmfence: add it to oe-core
> mesa: upgrade to 10.1.3
>
> .../mesa/{mesa-gl_9.2.5.bb => mesa-gl_10.1.3.bb} | 0
> meta/recipes-graphics/mesa/mesa.inc | 35 +++++++++++++---------
> .../mesa/{mesa_9.2.5.bb => mesa_10.1.3.bb} | 4 +--
> meta/recipes-graphics/mesa/mesa_git.bb | 4 +--
> meta/recipes-graphics/xorg-lib/libxshmfence_1.1.bb | 17 +++++++++++
> meta/recipes-graphics/xorg-proto/dri3proto_1.0.bb | 14 +++++++++
> 6 files changed, 56 insertions(+), 18 deletions(-)
> rename meta/recipes-graphics/mesa/{mesa-gl_9.2.5.bb => mesa-gl_10.1.3.bb} (100%)
> rename meta/recipes-graphics/mesa/{mesa_9.2.5.bb => mesa_10.1.3.bb} (82%)
> create mode 100644 meta/recipes-graphics/xorg-lib/libxshmfence_1.1.bb
> create mode 100644 meta/recipes-graphics/xorg-proto/dri3proto_1.0.bb
>
> --
> 1.9.1
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [OE-core] [PATCH 0/3] mesa upgrade
2014-05-13 15:28 ` [OE-core] [PATCH 0/3] mesa upgrade Burton, Ross
@ 2014-05-14 20:34 ` Otavio Salvador
2014-06-04 12:52 ` Martin Jansa
1 sibling, 0 replies; 6+ messages in thread
From: Otavio Salvador @ 2014-05-14 20:34 UTC (permalink / raw)
To: OpenEmbedded Devel List; +Cc: OE-core
On Tue, May 13, 2014 at 12:28 PM, Burton, Ross <ross.burton@intel.com> wrote:
> As this is a major release of Mesa I'm expecting breakage somewhere...
> Can BSP maintainers please test these patches if their machines build
> Mesa? I'm expecting machines that use mesa-gl to break if they don't
> just use the pure software drivers (so that's at least EMGD and if I
> recall correctly some ARM drivers).
Yes; we'll give it a try in meta-fsl-arm.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [OE-core] [PATCH 0/3] mesa upgrade
2014-05-13 15:28 ` [OE-core] [PATCH 0/3] mesa upgrade Burton, Ross
2014-05-14 20:34 ` Otavio Salvador
@ 2014-06-04 12:52 ` Martin Jansa
2014-06-04 14:24 ` Burton, Ross
2014-06-06 16:15 ` Burton, Ross
1 sibling, 2 replies; 6+ messages in thread
From: Martin Jansa @ 2014-06-04 12:52 UTC (permalink / raw)
To: openembedded-devel; +Cc: OE-core
[-- Attachment #1: Type: text/plain, Size: 2824 bytes --]
On Tue, May 13, 2014 at 04:28:42PM +0100, Burton, Ross wrote:
> Hi all,
Sorry for hi-jacking the thread, but since today even the older 9.2.5 is
failing to find native python-libxml2
config.log:
configure:8059: checking for python2
configure:8075: found
/OE/build/oe-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/python-native/python2
configure:8086: result: python2
configure:8103: checking python2 module: libxml2
configure:8112: result: no
configure:8118: error: failed to find required module libxml2
Any idea why it started to fail now?
> As this is a major release of Mesa I'm expecting breakage somewhere...
> Can BSP maintainers please test these patches if their machines build
> Mesa? I'm expecting machines that use mesa-gl to break if they don't
> just use the pure software drivers (so that's at least EMGD and if I
> recall correctly some ARM drivers).
>
> Ross
>
> On 13 May 2014 15:59, Valentin Popa <valentin.popa@intel.com> wrote:
> > mesa upgrade to 10.1.3
> >
> > The following changes since commit 40551859671a1c9da26cfdcda34da952c66ac8c2:
> >
> > qemu/local.conf.sample: Add sdl PACKAGECONFIG (2014-05-13 08:02:04 +0100)
> >
> > are available in the git repository at:
> >
> > git://git.yoctoproject.org/poky-contrib vpopa/mesa
> > http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=vpopa/mesa
> >
> > Valentin Popa (3):
> > dri3proto: add it to oe-core
> > libxshmfence: add it to oe-core
> > mesa: upgrade to 10.1.3
> >
> > .../mesa/{mesa-gl_9.2.5.bb => mesa-gl_10.1.3.bb} | 0
> > meta/recipes-graphics/mesa/mesa.inc | 35 +++++++++++++---------
> > .../mesa/{mesa_9.2.5.bb => mesa_10.1.3.bb} | 4 +--
> > meta/recipes-graphics/mesa/mesa_git.bb | 4 +--
> > meta/recipes-graphics/xorg-lib/libxshmfence_1.1.bb | 17 +++++++++++
> > meta/recipes-graphics/xorg-proto/dri3proto_1.0.bb | 14 +++++++++
> > 6 files changed, 56 insertions(+), 18 deletions(-)
> > rename meta/recipes-graphics/mesa/{mesa-gl_9.2.5.bb => mesa-gl_10.1.3.bb} (100%)
> > rename meta/recipes-graphics/mesa/{mesa_9.2.5.bb => mesa_10.1.3.bb} (82%)
> > create mode 100644 meta/recipes-graphics/xorg-lib/libxshmfence_1.1.bb
> > create mode 100644 meta/recipes-graphics/xorg-proto/dri3proto_1.0.bb
> >
> > --
> > 1.9.1
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [OE-core] [PATCH 0/3] mesa upgrade
2014-06-04 12:52 ` Martin Jansa
@ 2014-06-04 14:24 ` Burton, Ross
2014-06-04 17:12 ` Martin Jansa
2014-06-06 16:15 ` Burton, Ross
1 sibling, 1 reply; 6+ messages in thread
From: Burton, Ross @ 2014-06-04 14:24 UTC (permalink / raw)
To: OE-devel; +Cc: OE-core
On 4 June 2014 13:52, Martin Jansa <martin.jansa@gmail.com> wrote:
> Sorry for hi-jacking the thread, but since today even the older 9.2.5 is
> failing to find native python-libxml2
>
> config.log:
> configure:8059: checking for python2
> configure:8075: found
> /OE/build/oe-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/python-native/python2
> configure:8086: result: python2
> configure:8103: checking python2 module: libxml2
> configure:8112: result: no
> configure:8118: error: failed to find required module libxml2
>
> Any idea why it started to fail now?
Great. Can you share the config.log?
Ross
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [OE-core] [PATCH 0/3] mesa upgrade
2014-06-04 14:24 ` Burton, Ross
@ 2014-06-04 17:12 ` Martin Jansa
0 siblings, 0 replies; 6+ messages in thread
From: Martin Jansa @ 2014-06-04 17:12 UTC (permalink / raw)
To: openembedded-devel; +Cc: OE-core
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Wed, Jun 04, 2014 at 03:24:34PM +0100, Burton, Ross wrote:
> On 4 June 2014 13:52, Martin Jansa <martin.jansa@gmail.com> wrote:
> > Sorry for hi-jacking the thread, but since today even the older 9.2.5 is
> > failing to find native python-libxml2
> >
> > config.log:
> > configure:8059: checking for python2
> > configure:8075: found
> > /OE/build/oe-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/python-native/python2
> > configure:8086: result: python2
> > configure:8103: checking python2 module: libxml2
> > configure:8112: result: no
> > configure:8118: error: failed to find required module libxml2
> >
> > Any idea why it started to fail now?
>
> Great. Can you share the config.log?
This is from config.log, do you want whole file?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [OE-core] [PATCH 0/3] mesa upgrade
2014-06-04 12:52 ` Martin Jansa
2014-06-04 14:24 ` Burton, Ross
@ 2014-06-06 16:15 ` Burton, Ross
1 sibling, 0 replies; 6+ messages in thread
From: Burton, Ross @ 2014-06-06 16:15 UTC (permalink / raw)
To: OE-devel; +Cc: OE-core
On 4 June 2014 13:52, Martin Jansa <martin.jansa@gmail.com> wrote:
> Sorry for hi-jacking the thread, but since today even the older 9.2.5 is
> failing to find native python-libxml2
>
> config.log:
> configure:8059: checking for python2
> configure:8075: found
> /OE/build/oe-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/python-native/python2
> configure:8086: result: python2
> configure:8103: checking python2 module: libxml2
> configure:8112: result: no
> configure:8118: error: failed to find required module libxml2
>
> Any idea why it started to fail now?
Something else must have lost a python-libxml2 dependency recently
because Mesa needs it but doesn't have a declared dependency.
Ross
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-06-06 16:15 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <cover.1399993010.git.valentin.popa@intel.com>
2014-05-13 15:28 ` [OE-core] [PATCH 0/3] mesa upgrade Burton, Ross
2014-05-14 20:34 ` Otavio Salvador
2014-06-04 12:52 ` Martin Jansa
2014-06-04 14:24 ` Burton, Ross
2014-06-04 17:12 ` Martin Jansa
2014-06-06 16:15 ` Burton, Ross
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox