problem with SHLIBs and RDEPENDS

problem with SHLIBs and RDEPENDS

[Robert Schuster]

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

Hi,
I am trying to make the OpenJDK recipes 'OE ready'. One hard issue I am
facing has to do with the shlibs mechanism in OE.

In order to get OpenJDKs dependencies right its libraries and binaries
are checked for library dependencies. That is all fine and I would love
to activate that.

Actually we have three kinds of OpenJDK builds atm:
 - zero (interpreter only; but with enhancements on ARM to make it fly)
 - shark (zero interpreter plus JIT based on LLVM)
 - cacao (completely different runtime)

The binary version of those recipes all bring a libjvm.so. Theoretically
a user could install all three packages (you can do that in
Debian/Ubuntu for example). However when the shlibs mechanism is
activated it puts the first built openjdk variant into a registry and
all subsequent variants get a hard runtime dependency on that package
(e.g. openjdk-shark will depend on openjdk-zero if I built zero first)
although there is no technical reason for this.

So my question is: How can I solve this issue without resorting to:

EXCLUDE_FROM_SHLIBS = "1"

which I currently use and which has the bad side-effect of not having
openjdk's own dependencies. :(

Regards,
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 270 bytes --]

Re: problem with SHLIBs and RDEPENDS

[Koen Kooi]

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

On 17-06-10 10:18, Robert Schuster wrote:
> Hi,
> I am trying to make the OpenJDK recipes 'OE ready'. One hard issue I am
> facing has to do with the shlibs mechanism in OE.
> 
> In order to get OpenJDKs dependencies right its libraries and binaries
> are checked for library dependencies. That is all fine and I would love
> to activate that.
> 
> Actually we have three kinds of OpenJDK builds atm:
>  - zero (interpreter only; but with enhancements on ARM to make it fly)
>  - shark (zero interpreter plus JIT based on LLVM)
>  - cacao (completely different runtime)
> 
> The binary version of those recipes all bring a libjvm.so. Theoretically
> a user could install all three packages (you can do that in
> Debian/Ubuntu for example). However when the shlibs mechanism is
> activated it puts the first built openjdk variant into a registry and
> all subsequent variants get a hard runtime dependency on that package
> (e.g. openjdk-shark will depend on openjdk-zero if I built zero first)
> although there is no technical reason for this.
> 
> So my question is: How can I solve this issue without resorting to:
> 
> EXCLUDE_FROM_SHLIBS = "1"
> 
> which I currently use and which has the bad side-effect of not having
> openjdk's own dependencies. :(

Try:

PRIVATE_LIBS = "libjvm.so"

That will mark any libjvm.so in PACKAGES for that recipe as private and
it won't show up as a shlib provider. We use this in mozilla recipes.

regards,

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

iD8DBQFMGe6oMkyGM64RGpERAseXAKCZvjVHnmWXiZZki2uUZ5NFtpUeAQCgkxzj
e+36yRWm1gOSgT1epqOBlbM=
=Cg4e
-----END PGP SIGNATURE-----

Re: problem with SHLIBs and RDEPENDS

[Robert Schuster]

[-- Attachment #1: Type: text/plain, Size: 2424 bytes --]

Hey cool, thats it.

Am 17.06.2010 11:45, schrieb Koen Kooi:
> On 17-06-10 10:18, Robert Schuster wrote:
> > Hi,
> > I am trying to make the OpenJDK recipes 'OE ready'. One hard issue I am
> > facing has to do with the shlibs mechanism in OE.
>
> > In order to get OpenJDKs dependencies right its libraries and binaries
> > are checked for library dependencies. That is all fine and I would love
> > to activate that.
>
> > Actually we have three kinds of OpenJDK builds atm:
> > - zero (interpreter only; but with enhancements on ARM to make it fly)
> > - shark (zero interpreter plus JIT based on LLVM)
> > - cacao (completely different runtime)
>
> > The binary version of those recipes all bring a libjvm.so. Theoretically
> > a user could install all three packages (you can do that in
> > Debian/Ubuntu for example). However when the shlibs mechanism is
> > activated it puts the first built openjdk variant into a registry and
> > all subsequent variants get a hard runtime dependency on that package
> > (e.g. openjdk-shark will depend on openjdk-zero if I built zero first)
> > although there is no technical reason for this.
>
> > So my question is: How can I solve this issue without resorting to:
>
> > EXCLUDE_FROM_SHLIBS = "1"
>
> > which I currently use and which has the bad side-effect of not having
> > openjdk's own dependencies. :(
>
> Try:
>
> PRIVATE_LIBS = "libjvm.so"
>
> That will mark any libjvm.so in PACKAGES for that recipe as private and
> it won't show up as a shlib provider. We use this in mozilla recipes.
>
> regards,
>
> Koen

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


-- 
Besuchen Sie uns vom 09.06. bis zum 12.06. auf dem LinuxTag 2010
an unserem Stand „Fairtrade Software“ (Halle 7.2a. / Stand 123)!
⇒ Unsere Themen dieses Jahr ⇒ • Evolvis • Freedroidz • Portale •
• Identity and Access Management • Mobile Applikationen •

tarent Gesellschaft für Softwareentwicklung und IT-Beratung mbH
Geschäftsführer: Boris Esser, Elmar Geese
HRB AG Bonn 5168 - Ust-ID: DE122264941
http://www.tarent.com/

Heilsbachstr. 24, 53123 Bonn, fon +49 228 52675-0, fax +49 228 52675-25
Weigandufer 45, 12059 Berlin, fon +49 30 5682943-30, fax +49 228 52675-25




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 270 bytes --]