[Pacemaker] Strange build problem

[Andrew Beekhof]

2010/2/8 Ante Karamatić <ivoks at ubuntu.com>:
> Hi
>
> Today Ubuntu removed libuuid.la from uuid-dev package. That's a result of
> merge from Debian and Debian's policy
> http://wiki.debian.org/ReleaseGoals/LAFileRemoval, so this problem might
> affect Debian and other distributions.
>
> make trows error after libtool commits suicide:
>
> libtool: link: ranlib .libs/libcrmcommon.a
> /bin/sed: can't read /usr/lib/libuuid.la: No such file or directory
> libtool: link: `/usr/lib/libuuid.la' is not a valid libtool archive
> make[2]: *** [libcrmcommon.la] Error 1
> make[2]: Leaving directory
> `/home/ivoks/Cluster/pacemaker-1.0.7+hg20100203/lib/common'
>
> Now, the funniest thing is that after running make again, without cleaning
> the tree, it passes libcrmcommon.a and dies on next step:
>
> libtool: link: ranlib .libs/libcrmcluster.a
> /bin/sed: can't read /usr/lib/libuuid.la: No such file or directory
> libtool: link: `/usr/lib/libuuid.la' is not a valid libtool archive
> make[2]: *** [libcrmcluster.la] Error 1
> make[2]: Leaving directory
> `/home/ivoks/Cluster/pacemaker-1.0.7+hg20100203/lib/common'
>
> If one runs make enough times, it will eventually compile. Anyone has an
> idea what's going on? In libcrmcommon.la and others there's dependency_libs
> which includes /usr/lib/libuuid.la and other .la files.

Well libcrmcommon.la and friends are generated files... perhaps
re-running ./autogen.sh and configure would help.
How are you building?  From the raw mercurial tarball or from the
result of "make dist"?