Package: gobo
Version: 3.3-3
Severity: serious

Hi,

building the package gobo in a clean sid build environment
(with pbuilder) on i386 results in:

=========================================================================
[...]
dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; 
using uid of process (65534)
dpkg-source: building gobo using existing gobo_3.3.orig.tar.gz
dpkg-source: building gobo in gobo_3.3-3.diff.gz
dpkg-source: warning: executable mode 0755 of 
`debian/patches/gobo-compile.dpatch' will not be represented in diff
dpkg-source: warning: executable mode 0755 of 
`debian/patches/gobo-makefile.dpatch' will not be represented in diff
dpkg-source: building gobo in gobo_3.3-3.dsc
 debian/rules build
test -d debian/patched || install -d debian/patched
dpatch  apply-all  
applying patch gobo-makefile to ./ ... ok.
applying patch gobo-compile to ./ ... ok.
dpatch  cat-all  >>patch-stampT
mv -f patch-stampT patch-stamp
dh_testdir
cd src &&                       \
          SmartEiffel="/usr/lib/smarteiffel/sys/system.se"      \
          COMPILE="se-compile"          \
          GOBO="/tmp/buildd/gobo-3.3"           \
          CFLAGS="-Wall -g -O2"         \
          /usr/bin/make all
make[1]: Entering directory `/tmp/buildd/gobo-3.3/src'
/usr/bin/make -C geant
make[2]: Entering directory `/tmp/buildd/gobo-3.3/src/geant'
se-compile se.ace
make[2]: se-compile: Command not found
make[2]: *** [geant] Error 127
make[2]: Leaving directory `/tmp/buildd/gobo-3.3/src/geant'
make[1]: *** [geant] Error 2
make[1]: Leaving directory `/tmp/buildd/gobo-3.3/src'
make: *** [build-stamp] Error 2
=========================================================================

se-compile is located in /usr/lib/smarteiffel/bin. If it should be available
in a more common location, please coordinate with the smarteiffel maintainers.

Thanks for considering.


--
DARTS - Debian Archive Regression Test Suite
http://darts.alioth.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to