From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: nail@nslu2-linux.org, tim.ellis@foonas.org
Subject: mesa depending on samba or samba depending on extern talloc?
Date: Tue, 21 Dec 2010 14:35:50 +0100 [thread overview]
Message-ID: <20101221133550.GI3282@jama> (raw)
On 2010-10-20 I've pushed newer mesa-7.9
http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=30a3ea891d4511059a51882674f33aff2dddb96e
which depends on talloc
http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=fabce288e40037d28c70f0f034185176f85e8664
and separate talloc recipe (because building whole samba just to provide talloc for mesa seems wrong
and samba produced ICE before khem's fix)
http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=afce52663d6b5b79c097136fa794dd3f76a4afff
Today I noticed, that usr/lib/pkgconfig/talloc.pc from talloc recipe was enough for mesa to compile,
but because there was no libtalloc.so link it wasn't used in the end (as ldd confirms).
so talloc stages:
bitbake@jama ~ $ ll tmpdir-shr/sysroots/armv4t-oe-linux-gnueabi/usr/lib/libtalloc.*
-rwxr-xr-x 1 bitbake bitbake 32K Dec 21 13:30 tmpdir-shr/sysroots/armv4t-oe-linux-gnueabi/usr/lib/libtalloc.a
-rwxr-xr-x 1 bitbake bitbake 73K Dec 21 13:30 tmpdir-shr/sysroots/armv4t-oe-linux-gnueabi/usr/lib/libtalloc.so.2.0.1
bitbake@jama ~ $ ll tmpdir-shr/sysroots/armv4t-oe-linux-gnueabi/usr/lib/pkgconfig/talloc.pc
-rw-r--r-- 1 bitbake bitbake 251 Dec 21 13:30 tmpdir-shr/sysroots/armv4t-oe-linux-gnueabi/usr/lib/pkgconfig/talloc.pc
samba adds:
bitbake@jama ~ $ ll tmpdir-shr/sysroots/armv4t-oe-linux-gnueabi/usr/lib/libtalloc.*
lrwxrwxrwx 1 bitbake bitbake 14 Dec 14 13:33 tmpdir-shr/sysroots/armv4t-oe-linux-gnueabi/usr/lib/libtalloc.so -> libtalloc.so.1
-rwxr-xr-x 1 bitbake bitbake 123K Dec 14 13:33 tmpdir-shr/sysroots/armv4t-oe-linux-gnueabi/usr/lib/libtalloc.so.1
now for sure I don't want to install whole samba on target (just for libtalloc) so I have few options
1) fix talloc to install libtalloc.so -> libtalloc.so.2.0.1 (conflicts with samba in sysroot)
2a) move libtalloc to separate package in samba recipe and make mesa depending on samba
2b) move libtalloc to separate package in samba recipe in case someone builds
it before mesa, but still depend only on fixed talloc
3) fix talloc + force samba build to use already installed libtalloc instead of building own version
Option 3) looks best, but I'm not sure how tightly samba depends on talloc
and don't have time to test all samba versions we currently have
(3.0.23c, 3.0.34, 3.2.15, 3.3.0, 3.3.9, 3.5.6), so 2b) looks as easier fix.
CCed 2 samba maintainers (wrt MAINTAINERS file) or if there is someone who cares about samba
recipes: can you clean recipes/samba a bit and provide some feedback on talloc issue?
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next reply other threads:[~2010-12-21 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 13:35 Martin Jansa [this message]
2010-12-21 14:09 ` [PATCH 1/2] talloc: install .so links Martin Jansa
2010-12-21 16:26 ` Koen Kooi
2010-12-21 14:09 ` [PATCH 2/2] samba: use external talloc instead of building own Martin Jansa
2010-12-21 16:26 ` Koen Kooi
2010-12-21 15:11 ` mesa depending on samba or samba depending on extern talloc? Khem Raj
2010-12-21 16:39 ` 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=20101221133550.GI3282@jama \
--to=martin.jansa@gmail.com \
--cc=nail@nslu2-linux.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=tim.ellis@foonas.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.