Mailinglist Archive: opensuse-buildservice (261 mails)

< Previous Next >
[opensuse-buildservice] Factory does not see libidn ?
  • From: Amilcar do Carmo Lucas <webmaster@xxxxxxxxxxxx>
  • Date: Wed, 4 Jun 2008 12:13:10 +0200
  • Message-id: <200806041213.10473.webmaster@xxxxxxxxxxxx>
Hi all,

KDevelop builds fine for _ALL_ distros provided by the buildservice.
Thanks for the great job of the osbs people.

But one issue started to appear on Factory about a month ago:
/bin/sh ../../../libtool --silent --tag=CXX --mode=link
g++ -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align
-Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2
-fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -O2
-Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor
-fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE
-DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION
-avoid-version -no-undefined -L/opt/kde3/lib64 -L/usr/lib/qt3/lib64
-L/usr/lib64 -Wl,--as-needed -Wl,--enable-new-dtags -Wl,-Bsymbolic-functions -o
libcvsserviceintegrator.la -rpath /opt/kde3/lib64/kde3
cvsserviceintegrator.lo integratordlg.lo integratordlgbase.lo
fetcherdlgbase.lo
initdlg.lo ../../../lib/interfaces/extras/libkdevextras.la
../../../lib/libkdevelop.la -lcvsservice
grep: /usr/lib64/libidn.la: No such file or directory
/usr/bin/sed: can't read /usr/lib64/libidn.la: No such file or directory
libtool: link: `/usr/lib64/libidn.la' is not a valid libtool archive

Basically some part of the Factory distribution needs libidn for some reason.
I added lib-idn and libidn-devel to the Buildrequires of factory and it does
get installed, but factory still fails.

None of the other versions have this issue and all compile fine.

What is broken ?

--
Amilcar Lucas
Webmaster
The KDevelop project
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups