Package: vflib3
Version: 3.6.14-1
Severity: important
User: [EMAIL PROTECTED]
Usertags: ftbfs-xutils
From my pbuilder build log:
...
gcc -I../../src -I -g -O2 -g -Wall -O2 -g -Wall -pedantic -ansi
-DVFLIB_VERSION=\"3.6.14\" -DHYAKUX11 -c
hyakux11.c
rm -f hyakux11.c
../../libtool --mode=link \
gcc -g -O2 -g -Wall -O2 -g -Wall -pedantic -ansi
-DVFLIB_VERSION=\"3.6.14\" -o hyakux11
hyakux11.o \
../../src/libVFlib3.la -L
gcc -g -O2 -g -Wall -O2 -g -Wall -pedantic -ansi -DVFLIB_VERSION=\"3.6.14\" -o
.libs/hyakux11
hyakux11.o ../../src/.libs/libVFlib3.so -lttf -lt1 -lkpathsea -L/usr/lib -lnsl
-lm -L
gcc: argument to '-L' is missing
make[3]: *** [hyakux11] Error 1
make[3]: Leaving directory `/tmp/buildd/vflib3-3.6.14/utils/hyaku-1.1.0'
make[2]: *** [default] Error 2
make[2]: Leaving directory `/tmp/buildd/vflib3-3.6.14/utils'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/tmp/buildd/vflib3-3.6.14'
make: *** [build-stamp] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2
This is due to the following change in xutils 1:7.3+11:
* Remove the dependency of xutils against xutils-dev, it was only useful
for transitional purpose in Etch, closes: #418123.
My guess would be that the configure script is misusing the AC_PATH_X*
macro and trying to get a library path directly instead of using the
appropriate variable which would contain -L*. So if imake is installed, it
finds an explicit directory, but if it isn't, it detects the libraries are
in the system compiler paths and returns an empty string. (Note this is
just a guess without actually looking at the configure script.)
The current plan is to reintroduce the dependency for the lenny release,
then restore this change soon afterwards. At that point, this bug will
become RC.
--
Daniel Schepler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
