Hi Rinaldo,
On Thu, 2011-04-07 at 14:36 +0100, Rinaldo DiGiorgio wrote:
> /export/home/ips/bundles/6/jre.generate.depend has unresolved
> dependency 'depend fmri=__TBD pkg.debug.depend.file=libjvm.so
> pkg.debug.depend.path=lib pkg.debug.depend.path=usr/dt/lib/amd64
> pkg.debug.depend.path=usr/jdk/instances/1.6.0,5.11-105_jre/lib/amd64/xawt
> pkg.debug.depend.path=usr/jdk/instances/1.6.0,5.11-105_jre/lib/amd64/xawt/..
> pkg.debug.depend.path=usr/lib pkg.debug.depend.path=usr/openwin/lib/amd64
> pkg.debug.depend.reason=usr/jdk/instances/1.6.0,5.11-105_jre/lib/amd64/xawt/libmawt.so
> pkg.debug.depend.type=elf type=require' under the following combinations of
> variants:
> variant.arch:i386
Ok,
> The difference between the original manifest and the new manifest with
> dependencies seems to not have added dependencies other than internal
> ones.
Yes, that's because of the resolve failure you've got. Was this package
correctly resolving for you before?
'pkgdepend generate' for elf binaries, looks at the elf headers of the
file in question in order to determine the correct path to find
libjvm.so.
On my system,
for /usr/jdk/instances/jdk1.6.0/jre/lib/amd64/xawt/libmawt.so, elfdump
-d is reporting:
[12] RUNPATH 0x48f7 $ORIGIN:
$ORIGIN/..:/usr/dt/lib/amd64:/usr/openwin//lib/amd64
[13] RPATH 0x48f7 $ORIGIN:
$ORIGIN/..:/usr/dt/lib/amd64:/usr/openwin//lib/amd64
It's expanding $ORIGIN to /usr/jdk/instances/jdk1.6.0/jre/lib/amd64/xawt
but I wonder if the amd64 directory name is confusing it.
Does it resolve the 32-bit version of this library correctly? If so, I
think you might be hitting an instance of
https://defect.opensolaris.org/bz/show_bug.cgi?id=17808
You should be able to work around this by specifying a
pkg.depend.runpath in your manifest of
usr/jdk/instances/1.6.0,5.11-105_jre/lib/amd64:$PKGDEPEND_RUNPATH
cheers,
tim
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
