From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] giflib: don't link against libx11, don't depend on libsm
Date: Thu, 09 Feb 2012 19:50:09 +0100 [thread overview]
Message-ID: <jh14h2$866$1@dough.gmane.org> (raw)
In-Reply-To: <4F33BF11.4010009@opendreambox.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 09-02-12 13:41, Andreas Oberritter schreef:
> On 09.02.2012 01:54, Andreas Oberritter wrote:
>> On 08.02.2012 20:48, Otavio Salvador wrote:
>>> On Wed, Feb 8, 2012 at 17:35, Andreas Oberritter
>>> <obi@opendreambox.org>wrote:
>>>
>>>> I already explained in the commit message, why a PR bump is not
>>>> needed. Can you please explain which other possible failures you're
>>>> expecting, so I can learn why my reasoning may be wrong?
>>>>
>>>> This patch only fixes an unavailable build dependency at bitbake
>>>> level, nothing more.
>>>>
>>>
>>> Can the user call:
>>>
>>> bitbake libsm
>>>
>>> and then build giflib? in case of positive, we need to enforce have
>>> or not it linked.
>>
>> At the time I created the patch, the user couldn't run bitbake libsm
>> (for the same reason that it wouldn't be built automatically through
>> giflib's DEPENDS).
>>
>> That said, I updated the repos after your mail and ran bitbake libsm
>> in order to get the error message again, but the error vanished.
>> Apparently, an indirect dependency on libx11 was dropped during the
>> last few weeks. I searched the logs, but didn't find the change.
>> Strange. Now, many x11 packages got built even though x11 still wasn't
>> listed in my DISTRO_FEATURES.
>>
>> Anyway, please consider this patch obsolete. I'll probably resend an
>> updated version together with other patches to disable some more x11
>> libraries on demand.
>
> I did some further research regarding giflib:
>
> - giflib doesn't depend on libSM alone, but optionally depends on libX11.
> When linked against libX11, it also links agains libSM and libICE, under
> certain conditions. Since libSM does not depend on libX11, the current
> giflib build is non-deterministic.
>
> - Debian's/Ubuntu's giflib gets configured with --disable-x11
> unconditionally.
>
> So we have two options:
>
> 1.) Pass --disable-x11 unconditionally like Debian/Ubuntu 2.) Add
> virtual/libx11 to DEPENDS, if x11 is defined in DISTRO_FEATURES, and add
> --enable/diable-x11 to EXTRA_OECONF
I'd go for 1)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iEYEARECAAYFAk80FV4ACgkQMkyGM64RGpF1qQCdEZNQIneqMvodDIP02X3FLWtG
xYQAnj9BM2jzRHa6mPJDy4NfcYo28vHR
=iwwe
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-02-09 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 14:03 [meta-oe][PATCH] giflib: don't depend on libsm if x11 is unavailable Andreas Oberritter
2012-02-08 18:11 ` Andreas Oberritter
2012-02-08 18:41 ` Otavio Salvador
2012-02-08 19:35 ` Andreas Oberritter
2012-02-08 19:48 ` Otavio Salvador
2012-02-09 0:54 ` Andreas Oberritter
2012-02-09 12:41 ` [meta-oe][PATCH] giflib: don't link against libx11, don't depend on libsm Andreas Oberritter
2012-02-09 12:47 ` Otavio Salvador
2012-02-09 13:55 ` Paul Eggleton
2012-02-09 14:02 ` Paul Eggleton
2012-02-09 19:32 ` Henning Heinold
2012-02-09 18:50 ` Koen Kooi [this message]
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='jh14h2$866$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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