Re: Java defaults for kfreebsd-amd64
> On Tue, Jun 18, 2013 at 11:58:30PM +0200, Robert Millan wrote:
>> Are you sure those problems are not caused precisely because of gcj?
I wouldn't rule anything out yet... If Python is used as part of the
build system it could even be something to do with that (we still have
random thread-related issues sometimes building packages with waf).
On 19/06/13 07:48, Rene Engelhard wrote:
> [...]
> --with-jdk-home=/usr/lib/jvm/java-7-openjdk-kfreebsd-amd6
> [...]
> checking the installed JDK... checked (JDK 1.7.0_21)
> [...]
> and -I/usr/lib/jvm/java-7-openjdk-kfreebsd-amd64
> [...]
> And the tests run exactly $with_jdk_home/bin/java.
There are some curious mentions of gcj also in the failed build log.
https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=kfreebsd-amd64&ver=1%3A4.1.0~beta2-1&stamp=1370824274
> /«PKGBUILDDIR»/debian/rules check
> basename: missing operand
> Try `basename --help' for more information.
> dpkg-query: no path found matching pattern /usr/lib/x86_64-kfreebsd-gnu/gcj--*/libgcj_bc.so.1
> dpkg-query: error: --listfiles needs at least one package name argument
>
> Use --help for help about querying packages.
> dirname: missing operand
> Try `dirname --help' for more information.
> make[1]: Entering directory `/«PKGBUILDDIR»'
> t=`mktemp -q -d`; \
> cd . && \
> export PATH=/«PKGBUILDDIR»/debian/usr/bin:/usr/lib/jvm/java-gcj/bin:$PATH; \
> export TMPDIR=$t; \
> export HOME=$t; \
> export SAL_USE_VCLPLUGIN="svp"; \
> if [ -x /usr/bin/gdb ]; then ulimit -c unlimited; fi && \
> /usr/bin/make -k check || /usr/bin/make check && \
Regards,
--
Steven Chamberlain
steven@pyro.eu.org
Reply to: