[Pacemaker] Strange build problem

[Andrew Beekhof]

2010/2/9 Ante Karamatić <ivoks at grad.hr>:
> On 09.02.2010 12:42, Andrew Beekhof wrote:
>
>> Very odd.
>
> Indeed.
>
>> And the process is repeatable?
>
> Yes, every time same thing.
>
>> Perhaps attach compile logs and config.log
>
> Compile log:
>
> http://launchpadlibrarian.net/38892214/buildlog_ubuntu-lucid-amd64.pacemaker_1.0.7%2Bhg20100203-1ubuntu0ppa2_FAILEDTOBUILD.txt.gz
>
> Look for 'debian/rules build'. config.log is attached.

Its hard to blame pacemaker, the command its running is:

libtool: link: gcc -std=gnu99 -shared  .libs/ipc.o .libs/utils.o
.libs/xml.o .libs/iso8601.o .libs/iso8601_fields.o .libs/remote.o
.libs/mainloop.o   /usr/lib/libgnutls.so /usr/lib/libplumb.so
/usr/lib/libpils.so -lbz2 /usr/lib/libxslt.so /usr/lib/libxml2.so -lc
-luuid -lpam -lrt -ldl /usr/lib/libglib-2.0.so /usr/lib/libltdl.so
-Wl,-Bsymbolic-functions   -Wl,-soname -Wl,libcrmcommon.so.2 -o
.libs/libcrmcommon.so.2.0.0

Which clearly doesn't reference any .la files directly.

My guess is that there are other .la files on your (build) system that
contain references to /usr/lib/libuuid.la
Either that or perhaps pass --disable-static to configure

This may also help:
   http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-util/lafilefixer/files/lafilefixer-0.5?rev=1.1&view=markup