Your message dated Wed, 18 Oct 2006 21:50:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line gcj: command not found
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gjdoc
Version: 0.7.7-5
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of gjdoc_0.7.7-5 on lxdebian.bfinv.de by sbuild/s390 85
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>> 4), cdbs, gcj-4.1 (>= 4.1.1-15), fastjar, antlr
> (>= 2.7.1), tetex-bin, perl, python, time
[...]
> 75.42user 0.78system 1:17.63elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k
> 0inputs+0outputs (0major+271819minor)pagefaults 0swaps
> time gcj -g -O2 -o build-native/gjdoc \
> --main=gnu.classpath.tools.gjdoc.Main \
> -Dgnu.gcj.runtime.VMClassLoader.library_control=never \
> /usr/share/java/antlr.jar *.jar
> /bin/sh: gcj: command not found
>
> real 0m0.001s
> user 0m0.000s
> sys 0m0.000s
> make: *** [build-native-stamp] Error 127
> ******************************************************************************
> Build finished at 20061014-1925
> FAILED [dpkg-buildpackage died]
--- End Message ---
--- Begin Message ---
Version: 0.7.7-6
fixed
--- End Message ---
