Re: ORBit2-2.3.102 compile problem



Gregory Leblanc <gleblanc@linuxweasel.com> writes: 
> /bin/sh ../../libtool  --mode=install /usr/bin/install -c Everything_module.la /home/builder/var/tmp/ORBit2-2.3.102-root-local/usr/lib/orbit-2.0/Everything_module.la
> libtool: install: warning: relinking `Everything_module.la'
> cd /home/builder/projects/rpm/BUILD/ORBit2-2.3.102/test/everything; /bin/sh ../../libtool --mode=relink gcc -O2 -march=i386 -mcpu=i686 -o Everything_module.la -rpath /usr/lib/orbit-2.0 -export-dynamic -module everything-imodule.lo ../../src/orb/libORBit-2.la
> gcc -shared  everything-imodule.lo  -L/usr/lib -lORBit-2   -Wl,-soname -Wl,Everything_module.so.0 -o .libs/Everything_module.so.0.0.0
> /usr/bin/ld: cannot find -lORBit-2
> collect2: ld returned 1 exit status
> libtool: install: error: relink `Everything_module.la' with the above command before installing it
> libtool: install: warning: remember to run `libtool --finish /usr/lib/orbit-2.0'make[1]: Leaving directory `/home/builder/projects/rpm/BUILD/ORBit2-2.3.102/test/everything'
> 

Libtool is fucked, basically. 

That's why so many Red Hat spec files have this at the top:

 %define __libtoolize :

To keep the RPM macros from re-running libtoolize and ending up with a
broken libtool script that wants to relink things.

If the upstream package was created with a libtool that likes to
relink things, you have to patch ltmain.sh; thus all the Red Hat RPMs
containing a "fixed-ltmain.sh" file. The fix is essentially 
s/need_relink=yes/need_relink=no/g in ltmain.sh.

Relinking makes installing to a location other than the final
location, which is what an RPM requires, into an impossibility. 

Relinking is not required on Linux so can just be turned off.

Havoc



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]