On Sat, 2008-03-01 at 09:39 -0600, Peter O'Gorman wrote: > Steven Munroe wrote: > > I am trying to build a package on a OpenSuse-10.3 PowerMac G5. and I see > > the following: > > > > /bin/sh ../../libtool --tag=CC --mode=link /usr/bin/gcc -m64 -g -O2 > > -mcpu=power > > 4 -fno-strict-aliasing -Wdeclaration-after-statement -g -Wall -Wunused > > -Wmissing > > -prototypes -Wmissing-declarations -Wstrict-prototypes > > -Wmissing-prototypes -Wn > > ested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align > > -Wwrite-strings -m64 > > -o pedump pedump.o > > libmonoruntime.la ../io-layer/libwapi.la ../utils/libmonouti > > ls.la ../../libgc/libmonogc.la -pthread -lgthread-2.0 -lrt -lglib-2.0 > > -lm -ldl > > -lpthread -lm > > libtool: link: cannot find the library `/usr/lib64/libpcre.la' > > or unhandled argument `/usr/lib64/libpcre.la' > > It seems likely that some other .la file has /usr/lib64/libpcre.la in > its dependency_libs. If you add --debug immediately prior to the > --tag=CC and save stdout and stderr to a log, reading the log should > tell you which one. Alternatively, grep for /usr/lib64/libpcre.la in > /usr/lib64.
The dependency seem to be coming from /usr/lib64/libgthread-2.0.la at least on the system that is failing. The older (--debug output -> libtool-libpcre-ok.tgz) system does not seem to have the same dependency. I still don't understand why libtool does not simply link to the /usr/lib64/libpcre.so that is there? This is really annoying...
libtool-libpcre.tgz
Description: application/compressed-tar
libtool-libpcre-ok.tgz
Description: application/compressed-tar
_______________________________________________ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
