Maynard Johnson wrote: > Hi, Peter, > I posted to this list last winter regarding some problems I was having > integrating libtool into a project (the oprofile project) -- in particular, > building 64-bit on a bi-arch system (IBM POWER5). You helped with some usage > problems and also provided a fix in libtool 1.5.26. Now I'm trying to use > libtool in another project and having what looks like the exact symptom I > started out with in the oprofile project last winter. Here are the details: > > - libtool 1.5.26 installed in /usr/local > - removed existing aclocal.m4 in project root directory > - ran 'libtoolize --automake' and 'aclocal -I /usr/local/share/aclocal' from > project root directory (now see "# serial 52 AC_PROG_LIBTOOL" in aclocal.m4) > - run configure and make. The make fails as shown below: > > +++++++++++++++++ > [EMAIL PROTECTED]:~/SLES11_new/BUILD/Dpiperf/src/a2n> /bin/sh ../../libtool > --tag=CC --mode=link gcc -I../../include -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -DDEBUG -DAUTOMAKE -fPIC -shared > -g -O2 -m64 -o liba2n.la -rpath /usr/lib64 -version-info 11:0:0 > liba2n_la-a2n.lo liba2n_la-a2nint.lo liba2n_la-initterm.lo > liba2n_la-linuxsyms.lo liba2n_la-linuxelf.lo liba2n_la-linuxelf64.lo > liba2n_la-linuxmap.lo liba2n_la-linuxval.lo liba2n_la-saveres.lo > liba2n_la-util.lo -lbfd -liberty -ldl > gcc -shared .libs/liba2n_la-a2n.o .libs/liba2n_la-a2nint.o > .libs/liba2n_la-initterm.o .libs/liba2n_la-linuxsyms.o > .libs/liba2n_la-linuxelf.o .libs/liba2n_la-linuxelf64.o > .libs/liba2n_la-linuxmap.o .libs/liba2n_la-linuxval.o > .libs/liba2n_la-saveres.o .libs/liba2n_la-util.o /usr/lib/libbfd.so -liberty > -ldl -m64 -Wl,-soname -Wl,liba2n.so.11 -o .libs/liba2n.so.11.0.0 > /usr/lib/libbfd.so: could not read symbols: File in wrong format > collect2: ld returned 1 exit status > +++++++++++++++++ > By passing in LDFLAGS="-L/usr/lib64" to ./configure, I was able to get the project to build. This technique works with either libtool 1.5.22 or 1.5.26. Seems like a hack, though. I don't have to do this for the oprofile project, so I suspect I'm missing something here.
Thanks. -Maynard > > On this ppc64 system I'm developing on, the 64-bit BFD library is located in > /usr/lib64, but as you can see from above, the gcc command is specifying > /usr/lib/libbfd.so, which is the 32-bit library. > > Any idea what could be the problem? > > Thanks much for the help. > > -Maynard Johnson > _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool