From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Should be xserver-xorg MACHINE_ARCH?
Date: Mon, 01 Mar 2010 17:17:59 +0100 [thread overview]
Message-ID: <hmgpbo$l0e$1@dough.gmane.org> (raw)
In-Reply-To: <20100301144040.GB12022@jama>
-----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-----
next prev parent reply other threads:[~2010-03-01 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 14:40 Should be xserver-xorg MACHINE_ARCH? Martin Jansa
2010-03-01 16:17 ` Koen Kooi [this message]
2010-03-01 16:33 ` Martin Jansa
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='hmgpbo$l0e$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox