Should be xserver-xorg MACHINE_ARCH?

Should be xserver-xorg MACHINE_ARCH?

[Martin Jansa]

Today I was checking why building om-gta01 and om-gta02 in same tmpdir
fails with this error:

 * satisfy_dependencies_for: Cannot satisfy the following dependencies for task-shr-minimal-x:
 *      libdrm (>= 2.4.18+gitr4565+b5aec2bd3df736216e86eae28e278172d3ba3362) *  libdrm (>= 2.4.18+gitr4565+b5aec2bd3df736216e86eae28e278172d3ba3362) *  libdrm (>= 2.4.18+gitr4565+b5aec2bd3df736216e86eae28e278172d3ba3362) *

first I noticed that task-shr-minimal.bb was missing
PACKAGE_ARCH = "${MACHINE_ARCH}"
after I moved some machine specific depends there (from shr-image.inc).

But even after that setting PACKAGE_ARCH right, I have this error and I think 
it's because xserver-xorg was built first for om-gta02 with virtual/libgl 
provider set to mesa-dri (_git.bb version used) and resulting .ipk has armv4t
arch, even when it was built with machine specific virtual/libgl provider and
libdrm version also specific for om-gta02 (om-gta01 will use 2.4.18 release instead,
because it doesn't need glamo specific patches from libdrm_git.bb)

What is right solution? Set xserver-xorg arch to MACHINE_ARCH (as virtual/libgl is
usually decided based on target machine). Or force om-gta01 to use mesa-dri (I already
did) and also libdrm from git repo with glamo patches (because upstream git repo and 
glamo repo has different SRCREV so switching to libdrm_git.bb won't help).

Thanks!

Regards,

BTW: I think we're going to have the same problems as when someone want's to build different
distributions in same tmpdir.

Looks like I should always use distro override instead machine override, because with machine
override I'm creating the same problem as above for other distributions building more machines
in same tmpdir.

-- 
uin:136542059                jid:Martin.Jansa@gmail.com
Jansa Martin                 sip:jamasip@voip.wengo.fr 
JaMa                         

Re: Should be xserver-xorg MACHINE_ARCH?

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01-03-10 15:40, Martin Jansa wrote:
> Today I was checking why building om-gta01 and om-gta02 in same tmpdir
> fails with this error:
> 
>  * satisfy_dependencies_for: Cannot satisfy the following dependencies for task-shr-minimal-x:
>  *      libdrm (>= 2.4.18+gitr4565+b5aec2bd3df736216e86eae28e278172d3ba3362) *  libdrm (>= 2.4.18+gitr4565+b5aec2bd3df736216e86eae28e278172d3ba3362) *  libdrm (>= 2.4.18+gitr4565+b5aec2bd3df736216e86eae28e278172d3ba3362) *
> 
> first I noticed that task-shr-minimal.bb was missing
> PACKAGE_ARCH = "${MACHINE_ARCH}"
> after I moved some machine specific depends there (from shr-image.inc).
> 
> But even after that setting PACKAGE_ARCH right, I have this error and I think 
> it's because xserver-xorg was built first for om-gta02 with virtual/libgl 
> provider set to mesa-dri (_git.bb version used) and resulting .ipk has armv4t
> arch, even when it was built with machine specific virtual/libgl provider and
> libdrm version also specific for om-gta02 (om-gta01 will use 2.4.18 release instead,
> because it doesn't need glamo specific patches from libdrm_git.bb)
> 
> What is right solution? Set xserver-xorg arch to MACHINE_ARCH (as virtual/libgl is
> usually decided based on target machine). Or force om-gta01 to use mesa-dri (I already
> did) and also libdrm from git repo with glamo patches (because upstream git repo and 
> glamo repo has different SRCREV so switching to libdrm_git.bb won't help).

Part of the solution is to stop making mesa machine specific when no
machine specific are in use (e.g. using swrast).

The next step would be to add some magic to the xserver-xorg recipes to
make it ${MACHINE_ARCH} only when mesa is ${MACHINE_ARCH}.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLi+i3MkyGM64RGpERAgioAJ92mWsOlQQ2wBp9WlMT15RYpRsgzwCaAv7J
Jwg7AvYkE0LPsLpZshPMLlw=
=J9CM
-----END PGP SIGNATURE-----

Re: Should be xserver-xorg MACHINE_ARCH?

[Martin Jansa]

On Mon, Mar 01, 2010 at 05:17:59PM +0100, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 01-03-10 15:40, Martin Jansa wrote:
> > Today I was checking why building om-gta01 and om-gta02 in same tmpdir
> > fails with this error:
> > 
> >  * satisfy_dependencies_for: Cannot satisfy the following dependencies for task-shr-minimal-x:
> >  *      libdrm (>= 2.4.18+gitr4565+b5aec2bd3df736216e86eae28e278172d3ba3362) *  libdrm (>= 2.4.18+gitr4565+b5aec2bd3df736216e86eae28e278172d3ba3362) *  libdrm (>= 2.4.18+gitr4565+b5aec2bd3df736216e86eae28e278172d3ba3362) *
> > 
> > first I noticed that task-shr-minimal.bb was missing
> > PACKAGE_ARCH = "${MACHINE_ARCH}"
> > after I moved some machine specific depends there (from shr-image.inc).
> > 
> > But even after that setting PACKAGE_ARCH right, I have this error and I think 
> > it's because xserver-xorg was built first for om-gta02 with virtual/libgl 
> > provider set to mesa-dri (_git.bb version used) and resulting .ipk has armv4t
> > arch, even when it was built with machine specific virtual/libgl provider and
> > libdrm version also specific for om-gta02 (om-gta01 will use 2.4.18 release instead,
> > because it doesn't need glamo specific patches from libdrm_git.bb)
> > 
> > What is right solution? Set xserver-xorg arch to MACHINE_ARCH (as virtual/libgl is
> > usually decided based on target machine). Or force om-gta01 to use mesa-dri (I already
> > did) and also libdrm from git repo with glamo patches (because upstream git repo and 
> > glamo repo has different SRCREV so switching to libdrm_git.bb won't help).

Thanks for feedback!
 
> Part of the solution is to stop making mesa machine specific when no
> machine specific are in use (e.g. using swrast).

But for om-gta01 we use swrast, for gta02 swrast and glamo, so it needs
to be machine specific here, or I'm missing the point :/.

> The next step would be to add some magic to the xserver-xorg recipes to
> make it ${MACHINE_ARCH} only when mesa is ${MACHINE_ARCH}.

And what about different virtual/libgl providers? It will be even more
hackish magic to check if all machines are sharing the same provider or
not IMHO.

BTW: already pushed change from machine overrides to distro overrides,
then I was able to build gta01 image fine, but still not very happy with
it.

Regards,

-- 
uin:136542059                jid:Martin.Jansa@gmail.com
Jansa Martin                 sip:jamasip@voip.wengo.fr 
JaMa