Re: Re: Where is libjawt.so located ?
On Thu, Sep 10, 2009 at 8:50 AM, Sylvestre Ledru <sylvestre@debian.org> wrote:
> Le mercredi 02 septembre 2009 à 11:56 -0400, Dominique Belhachemi a
> écrit :
>> > http://packages.debian.org/search?suite=sid&searchon=contents&keywords=libjawt.so
>>
>> I am wondering if there is a transition ongoing from 'powerpc' to 'ppc' or vice versa ?
> I don't think there is any transition. It is just that, as far as I know, there is no perfect match or
> easy way to get the matching "debian arch name" with "java arch name".
>
> (I would be happy to know that I am wrong)
Most java package are pretty smart and to avoid this kind of headache
provide a proper symlink:
$ ls -al /usr/lib/jvm/default-java/lib/libjawt.so
lrwxrwxrwx 1 root root 30 2009-07-15 16:05
/usr/lib/jvm/default-java/lib/libjawt.so ->
../../../gcj-4.3-90/libjawt.so
Except it does not work on armel:
https://buildd.debian.org/~luk/status/package.php?p=gdcm#fail-gdcm-armel
[ 88%] Building CXX object
Utilities/VTK/CMakeFiles/vtkgdcmJava.dir/vtkGDCMThreadedImageReader2Java.cxx.o
make[3]: *** No rule to make target
`/usr/lib/jvm/default-java/lib/libjawt.so', needed by
`bin/libvtkgdcmJava.so'. Stop.
make[3]: Leaving directory
`/build/buildd-gdcm_2.0.12-11-armel-vYWMSv/gdcm-2.0.12/debian/build-python2.5'
make[2]: *** [Utilities/VTK/CMakeFiles/vtkgdcmJava.dir/all] Error 2
make[2]: Leaving directory
`/build/buildd-gdcm_2.0.12-11-armel-vYWMSv/gdcm-2.0.12/debian/build-python2.5'
make[1]: *** [all] Error 2
Which I also forwarded to :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544674
CMake is now holding back VTK which is holding back GDCM which is
holding back ITK.
--
Mathieu
Reply to: