Adriaan de Groot wrote: > This is the tail end of BDB compilation: > > nsl -lc -z combreloc -z redlocsym -z nodefaultlib -z ignore -z now -z > rescan -z > absexec -xipo=0 -xldscope=symbolic -xlibmil -s -xtarget=opteron -m64 > -xarch=sse2 -xchip=opteron -xcache=64/64/2:1024/64/16 -mt > libtool: compile: cannot determine name of library object from > `.libs/libdb-4.2.so' > > on dillon right now. I suppose that means that libtool is (again) borked. Or > the Makefiles, as I see that a libtool --link is invoked, which *re*invokes > libtool without a mode or tag specified. > > [ade]
libtool strikes again! i remember something about bdb's build system that it does not create the correct *.lo files (the libtool wrappers for the *.o files which are to be found under ./.libs/*.o). So, please check for 2 b0rked things: 1. the existence of the *.lo libtool wrapper files in $(dir)/foo/ 2. the existence of the corresponding *.o object files under $(dir)/foo/.libs/*.o --Stefan -- Stefan Teleman Sun Microsystems, Inc. stefan.teleman at Sun.COM
