[bind10-dev] why does LOG4CPLUS_LDFLAGS have MULTITHREADING_FLAG?

[Jelte Jansen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/10/2011 01:30 AM, JINMEI Tatuya / 神明達哉 wrote:
> According to git blame, you added the following line to configure.ac:
> 
> 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).

But perhaps i'm just missing some automake/libtool voodoo again.

Jelte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3xzasACgkQ4nZCKsdOncWr4QCfdYQD2bqASHxrxKBJzvF8g7MJ
9MkAmgIIZaIkhzhb1sGAS+Kz7MWB3qcn
=pgu+
-----END PGP SIGNATURE-----