Mailinglist Archive: opensuse-packaging (165 mails)

< Previous Next >
Re: [opensuse-packaging] Why package builds for Factory but fails for 12.2?
On Fri, 2012-07-06 at 13:46 +0400, Ilya Chernykh wrote:
The configure script says it cannot find dar/libdar.hpp but this file is part
of libdar-devel and this
package in the same in 12.2 and Factory. So possibly the lookup path is
somehow broken
in 12.2.

The link:


frankly, for somebody that is 'maintaining' a package you make your life
always very easy by just asking why your package does not build anymore.
No hints of what you verified (if anything at all) and what you tried.

We could as well argue that actually not you, but the big part of
readers of this mailing list with a good heart are maintaining KDE3.

Now, that was enough of ranting, down to business.

Reading config.log of the failed build, reveals:
configure:27892: g++ -c -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 -O2 -Wall -D_FORTIFY_SOURCE=2
-fstack-protector -funwind-tables -fasynchronous-unwind-tables -g
-Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor
-fno-exceptions -fno-check-new -fno-common -fexceptions
In file included from /usr/include/dar/my_config.h:32:0,
from /usr/include/dar/libdar.hpp:50,
from conftest.cpp:79:
/usr/include/dar/config.h:89:0: error: unterminated #ifndef
configure:27892: $? = 1

So yes,: this can not be built like this (and the result for configure
is interpreted as 'header not found'; call it a limitation of

Now, as the error suggests, the file /usr/include/dar/config.h is
'corrupt', right? Let's look at the file:

The last 4 lines are:
#define LIBDAR_VERSION "2.3.10"

So yes, #ifndef is clearly not closed and thus results (correctly) in
this compiler error.

Now back to you, to actually do the fixing work right?

Dominique / DimStar

To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups