On Thu, 2013-01-10 at 11:44 -0500, Ken Giusti wrote:
> Hi Justin,
> 
> I have hit a problem testing RC4 on my debian-6 i686 VM:
> 
> I pulled down qpid-0.20.tar, did "./bootstrap && ./configure && make && make 
> test"  - all fine, but when I tried to 'make install' as root:
> 
> libtool: relink: g++ -shared -nostdlib 
> /usr/lib/gcc/i486-linux-gnu/4.4.5/../../../../lib/crti.o 
> /usr/lib/gcc/i486-linux-gnu/4.4.5/crtbeginS.o  qpid/ha/.libs/Backup.o 
> qpid/ha/.libs/BrokerInfo.o qpid/ha/.libs/BrokerReplicator.o 
> qpid/ha/.libs/ConnectionObserver.o qpid/ha/.libs/HaBroker.o 
> qpid/ha/.libs/HaPlugin.o qpid/ha/.libs/Membership.o qpid/ha/.libs/Primary.o 
> qpid/ha/.libs/QueueGuard.o qpid/ha/.libs/QueueReplicator.o 
> qpid/ha/.libs/ReplicatingSubscription.o qpid/ha/.libs/ReplicationTest.o 
> qpid/ha/.libs/StatusCheck.o qpid/ha/.libs/RemoteBackup.o 
> qpid/ha/.libs/types.o   -L/usr/local/lib -lqpidbroker -lqpidmessaging 
> -L/usr/lib/gcc/i486-linux-gnu/4.4.5 
> -L/usr/lib/gcc/i486-linux-gnu/4.4.5/../../../../lib -L/lib/../lib 
> -L/usr/lib/../lib -L/usr/lib/gcc/i486-linux-gnu/4.4.5/../../.. 
> -L/usr/lib/i486-linux-gnu -lstdc++ -lm -lc -lgcc_s 
> /usr/lib/gcc/i486-linux-gnu/4.4.5/crtendS.o 
> /usr/lib/gcc/i486-linux-gnu/4.4.5/../../../../lib/crtn.o    -Wl,-soname 
> -Wl,ha.so -o .libs/ha.so
> /usr/bin/ld: cannot find -lqpidbroker
> collect2: ld returned 1 exit status
> libtool: install: error: relink `ha.la' with the above command before 
> installing it
> make[3]: *** [install-dmoduleexecLTLIBRARIES] Error 1
> 
> 
> This appears to be related to the automake configuration: I then tried to 
> rebuild using cmake, I was able to 'make install' from the cmake build tree 
> without a problem.

It looks like a missing dependency: qpidbroker needs to be installed
first for the install relink to find it.

Or perhaps the default install location /usr/local/lib isn't in the ld
path for some reason.

Andrew



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to