[bind10-dev] why does LOG4CPLUS_LDFLAGS have MULTITHREADING_FLAG?

[JINMEI Tatuya / 神明達哉]

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
> > 
> 
> Even without that flag, it still fails for me, I think that log4cplus install
> there has a similar problem itself; I can only get my bind10 to compile if i use
> a liblog4cplus with threading explicitely disabled (and then it does not appear
> to matter if i leave this flag above in).

Do you mean, by "for me", your personal (probably Linux) system, or
your own attempt to fix it on Solaris+SunStudio?  If it's the latter,
see #1006.  If it's the former, perhaps #1006 still has some hint;
log4cplus's ax_pthread.m4 may specify a bad default for other systems
and you may be able to work it around by setting PTHREAD_CFLAGS
appropriately.

> 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" :-)

---
JINMEI, Tatuya