Bug#493992: jcc FTBFS on everything except amd64 due to wrong paths (was jcc_1.9-4(sparc/unstable): FTBFS on sparc, missing dependency)

2008-08-07 Thread peter green
Jeff Breidenbach wrote: Peter, Thank you very much for the patch. It is almost right. Open JDK 1.6 has this really weird setup where one of the shared libraries is under the server subdirectory on AMD64 and under the client subdirectory under i386. (Not sure what the story is on other

Bug#493992: jcc FTBFS on everything except amd64 due to wrong paths (was jcc_1.9-4(sparc/unstable): FTBFS on sparc, missing dependency)

2008-08-07 Thread peter green
The PyLucene binary has almost exactly the same problem if you are interested in looking at that one too. PyLucene seems to build fine in my i386 sid chroot using the jcc built using my patch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact

Bug#493992: jcc FTBFS on everything except amd64 due to wrong paths (was jcc_1.9-4(sparc/unstable): FTBFS on sparc, missing dependency)

2008-08-07 Thread Jeff Breidenbach
What library is that? libjvm.so Specifically /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client/libjvm.so As found here: http://packages.debian.org/sid/i386/openjdk-6-jre-headless/filelist I'm surprised you got PyLucene to build; I wonder if it runs (there is a simple test in the PyLucene

Bug#493992: jcc FTBFS on everything except amd64 due to wrong paths (was jcc_1.9-4(sparc/unstable): FTBFS on sparc, missing dependency)

2008-08-07 Thread peter green
Jeff Breidenbach wrote: What library is that? libjvm.so Specifically /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client/libjvm.so As found here: http://packages.debian.org/sid/i386/openjdk-6-jre-headless/filelist checking packages.debian.org it seems that file is in the server

Bug#493992: jcc FTBFS on everything except amd64 due to wrong paths (was jcc_1.9-4(sparc/unstable): FTBFS on sparc, missing dependency)

2008-08-07 Thread peter green
I'm surprised you got PyLucene to build; I wonder if it runs (there is a simple test in the PyLucene README.Debian) From my i386 chroot with jcc built with my patch and pylucene built using the jcc built with my patch and unmodified source. debian:/# python Python 2.5.2 (r252:60911, Jul

Bug#493992: jcc FTBFS on everything except amd64 due to wrong paths (was jcc_1.9-4(sparc/unstable): FTBFS on sparc, missing dependency)

2008-08-07 Thread Jeff Breidenbach
Sounds good to me. Will apply and upload your patch today. Thanks for the hard work. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#493992: jcc FTBFS on everything except amd64 due to wrong paths (was jcc_1.9-4(sparc/unstable): FTBFS on sparc, missing dependency)

2008-08-07 Thread Jeff Breidenbach
Uploaded. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#493992: jcc FTBFS on everything except amd64 due to wrong paths (was jcc_1.9-4(sparc/unstable): FTBFS on sparc, missing dependency)

2008-08-06 Thread peter green
retitle 493992 jcc FTBFS on everything except amd64 due to wrong paths. thanks Reading the build log carefully this doesn't look like a missing dependency error to me (openjdk-6-jdk which depends on openjdk-6-jre which depends on openjdk-6-jre-headless which provides the libjvm.so is indeed

Bug#493992: jcc FTBFS on everything except amd64 due to wrong paths (was jcc_1.9-4(sparc/unstable): FTBFS on sparc, missing dependency)

2008-08-06 Thread Jeff Breidenbach
Peter, Thank you very much for the patch. It is almost right. Open JDK 1.6 has this really weird setup where one of the shared libraries is under the server subdirectory on AMD64 and under the client subdirectory under i386. (Not sure what the story is on other architectures). The PyLucene