Re: Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[Andrey Rahmatullin]

On Fri, May 18, 2018 at 07:04:08PM -0400, A. Maitland Bottoms wrote:
> If the problem can be traced to the .pc file and pkg-config I will take blame 
> for a bug.  I am away from an appropriate computer right now, but will 
> investigate further soon.
No, the configure script doesn't use pkg-config.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[A. Maitland Bottoms]

If the problem can be traced to the .pc file and pkg-config I will take blame 
for a bug.  I am away from an appropriate computer right now, but will 
investigate further soon.

-Maitland


On May 18, 2018 7:20:55 AM EDT, Andrey Rahmatullin  wrote:
>On Fri, May 18, 2018 at 01:06:18PM +0200, Andreas Tille wrote:
>> > The reason for this: the configure script compiles the following
>code:
>> > 
>> > #include 
>> > #include 
>> > int main() { std::cout << 1 << '\t' << 0; return 0; }
>> > 
>> > in order to check that  exists.
>> > But this code still requires -llog4cpp:
>> 
>> Thanks for the explanation but may be I'm missing your point.  The
>> package installs liblog4cpp.a as well and the dynamic library
>installs
>> the according .so file.  So why should the requriement -llog4cpp not
>> fulfilled?
>The configure script doesn't pass -llog4cpp. It tests for the existence
>of
>the header and tries to find a correct -I option for it. Finding the
>correct -L is the next step.
>
>> > /tmp/cc41MUW4.o: In function
>`__static_initialization_and_destruction_0(int, int)':
>> > 2.cpp:(.text+0x5b): undefined reference to
>`log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()'
>> > 2.cpp:(.text+0x70): undefined reference to
>`log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()'
>> > collect2: error: ld returned 1 exit status
>> 
>> Isn't this rather a bug in log4cpp?
>No.
>
>-- 
>WBR, wRAR

Re: Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[Andrey Rahmatullin]

On Fri, May 18, 2018 at 01:06:18PM +0200, Andreas Tille wrote:
> > The reason for this: the configure script compiles the following code:
> > 
> > #include 
> > #include 
> > int main() { std::cout << 1 << '\t' << 0; return 0; }
> > 
> > in order to check that  exists.
> > But this code still requires -llog4cpp:
> 
> Thanks for the explanation but may be I'm missing your point.  The
> package installs liblog4cpp.a as well and the dynamic library installs
> the according .so file.  So why should the requriement -llog4cpp not
> fulfilled?
The configure script doesn't pass -llog4cpp. It tests for the existence of
the header and tries to find a correct -I option for it. Finding the
correct -L is the next step.

> > /tmp/cc41MUW4.o: In function 
> > `__static_initialization_and_destruction_0(int, int)':
> > 2.cpp:(.text+0x5b): undefined reference to 
> > `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()'
> > 2.cpp:(.text+0x70): undefined reference to 
> > `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()'
> > collect2: error: ld returned 1 exit status
> 
> Isn't this rather a bug in log4cpp?
No.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[Andreas Tille]

Hi Andrey,

On Fri, May 18, 2018 at 03:05:24PM +0500, Andrey Rahmatullin wrote:
> On Fri, May 18, 2018 at 11:44:02AM +0200, Andreas Tille wrote:
> > > Checking for liblog4cpp...
> > > 
> > > Cannot continue since you don't seem to have log4cpp installed
> > > Please install the log4cpp-dev package and run configure again.
> > > make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2
> The reason for this: the configure script compiles the following code:
> 
> #include 
> #include 
> int main() { std::cout << 1 << '\t' << 0; return 0; }
> 
> in order to check that  exists.
> But this code still requires -llog4cpp:

Thanks for the explanation but may be I'm missing your point.  The
package installs liblog4cpp.a as well and the dynamic library installs
the according .so file.  So why should the requriement -llog4cpp not
fulfilled?
 
> /tmp/cc41MUW4.o: In function `__static_initialization_and_destruction_0(int, 
> int)':
> 2.cpp:(.text+0x5b): undefined reference to 
> `log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()'
> 2.cpp:(.text+0x70): undefined reference to 
> `log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()'
> collect2: error: ld returned 1 exit status

Isn't this rather a bug in log4cpp?
 
Kind regards

  Andreas.

-- 
http://fam-tille.de

Re: Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[Andrey Rahmatullin]

On Fri, May 18, 2018 at 11:44:02AM +0200, Andreas Tille wrote:
> > Checking for liblog4cpp...
> > 
> > Cannot continue since you don't seem to have log4cpp installed
> > Please install the log4cpp-dev package and run configure again.
> > make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2
The reason for this: the configure script compiles the following code:

#include 
#include 
int main() { std::cout << 1 << '\t' << 0; return 0; }

in order to check that  exists.
But this code still requires -llog4cpp:

/tmp/cc41MUW4.o: In function `__static_initialization_and_destruction_0(int, 
int)':
2.cpp:(.text+0x5b): undefined reference to 
`log4cpp::Appender::AppenderMapStorageInitializer::AppenderMapStorageInitializer()'
2.cpp:(.text+0x70): undefined reference to 
`log4cpp::Appender::AppenderMapStorageInitializer::~AppenderMapStorageInitializer()'
collect2: error: ld returned 1 exit status

As the configure script first searches for the header and only then for library
there appears to be no way to fix this apart from searching for some other
header that doesn't require linking the library (if that exists).

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: Bug#898964: mrs: FTBFS: you don't seem to have log4cpp installed

[Andreas Tille]

Control: tags -1 help

On Thu, May 17, 2018 at 11:15:17PM +0200, Dominic Hargreaves wrote:
> Whilst test-rebuilding packages for the next perl release we found
> an unrelated build failure:
> 
> Checking for liblog4cpp...
> 
> Cannot continue since you don't seem to have log4cpp installed
> Please install the log4cpp-dev package and run configure again.
> make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2
> 
> The full log is here:
> 
> 
> 
> This seems likely to be caused by the new release of log4cpp 1.1.3-1
> last week.

Most probably that is the reason - but how to solve this?  I admit I
have no idea. :-(

Kind regards

  Andreas.

-- 
http://fam-tille.de