The option -L/usr/lib is not in this package's build system per-se, but
rather in libtool which is invoked automatically by the autotools-based
build system. The relevant portion of the build log is:
/bin/bash ./libtool --tag=CXX --mode=link g++ -Wall -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -Wl,-z,relro -o libclippoly.la -rpath
/usr/lib/mips64el-linux-gnuabi64 nclip.lo poly.lo poly_io.lo posadder.lo
primitives.lo templates.lo version.lo graphadd.lo graphmat.lo
graphmat++.lo
libtool: link: g++ -fPIC -DPIC -shared -nostdlib
/usr/lib/gcc/mips64el-linux-gnuabi64/4.8/../../../mips64el-linux-gnuabi64/crti.o
/usr/lib/gcc/mips64el-linux-gnuabi64/4.8/crtbeginS.o .libs/nclip.o
.libs/poly.o .libs/poly_io.o .libs/posadder.o .libs/primitives.o
.libs/templates.o .libs/version.o .libs/graphadd.o .libs/graphmat.o
.libs/graphmat++.o -L/usr/lib/gcc/mips64el-linux-gnuabi64/4.8
-L/usr/lib/gcc/mips64el-linux-gnuabi64/4.8/../../../mips64el-linux-gnuabi64
-L/usr/lib/gcc/mips64el-linux-gnuabi64/4.8/../../../../lib
-L/lib/mips64el-linux-gnuabi64 -L/lib/../lib
-L/usr/lib/mips64el-linux-gnuabi64 -L/usr/lib/../lib
-L/usr/lib/gcc/mips64el-linux-gnuabi64/4.8/../../.. -lstdc++ -lm -lc
-lgcc_s /usr/lib/gcc/mips64el-linux-gnuabi64/4.8/crtendS.o
/usr/lib/gcc/mips64el-linux-gnuabi64/4.8/../../../mips64el-linux-gnuabi64/crtn.o
-O2 -Wl,-z -Wl,relro -Wl,-soname -Wl,libclippoly.so.0 -o
.libs/libclippoly.so.0.0.0
Note how libtool is invoked without the problematic option, but
libtool's invocation of g++ does contain the option.
The package uses dh-autoreconf to refresh the autotools files at build
time, so the problem cannot be due to an old version of libtool being
present in the package's sources.
For this reason, I'd suggest you either close this bug report, or
reassign it to the package containing the problematic libtool script.
Cheers,
--Barak.
--
Barak A. Pearlmutter
Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
http://www.bcl.hamilton.ie/~barak/
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
