[bind10-dev] why does LOG4CPLUS_LDFLAGS have MULTITHREADING_FLAG?

[Stephen Morris]

On 10/06/2011 09:21, JINMEI Tatuya / 神明達哉 wrote:
> At Fri, 10 Jun 2011 09:54:19 +0200,
> Jelte Jansen <jelte at isc.org> wrote:
> 
>>> 4fcd0d31 (Stephen Morris        2011-05-19 13:52:58 +0100 474) LOG4CPLUS_LDFLAGS="$LOG4CPLUS_LDFLAGS -llog4cplus $MULTITHREADING_FLAG"
>>>
>>> Is there any specific reason why you add this to "LDFLAGS"?  It seems
>>> MULTITHREADING_FLAG is generally compiler flags, not for the linker.
>>> I'm asking this because specifying a compiler flag in LDFLAGS can be
>>> very harmful as we saw in
>>> http://bind10.isc.org/~tester/builder/BIND10/20110609145000-Solaris10-sparc-Sunstudio/logs/build.out

No reason - I just copied configure.ac Jeremy used for his tests of
log4cplus on the build farm.

However, I suspect that at some point we do need to review the
configure.ac and our Makefile.am files.  In addition to ticket 1006 I
note that ticket 994 is concerned with sorting out the LDFLAGS/LIBS
confusion.

>> But perhaps i'm just missing some automake/libtool voodoo again.
> 
> When I figured this out, I tweeted, "libtool is very useful, but as it
> has so much of magic behind the scene, it's very difficult to debug
> once it doesn't work as expected" :-)

I've found the book "Autotools - A Practitioner's Guide to GNU Autoconf,
Automake and Libtool" by John Calcote to be a useful guide to these
black arts.

Stephen