On Wed, September 29, 2010 02:43, Bob Hetzel wrote:
[SNIP]
>
> If I can add another data point into this... I'm running configure for
> bacula 5.0.3 on RedHat Beta Enterprise Linux 6 beta refresh 2. The thread
> safe detection fails for my configure too.
[SNIP]
>
> however as suggested above, doing nm -D produces a different result
> # nm -D /usr/lib64/mysql/libmysqlclient_r.so |grep pthread_mutex_lock
> U pthread_mutex_lock
>
> Would I be safe if I just change my configure script to pass this test?
That is what I would do, as that is what I did to get it to work on my
system.
> Could the detection be changed somehow to make it more robust?
This is starting to look a little bit more complicated that I originally
thought - it may be necessary to write an entire program that goes off and
tries all the various possible combinations, which probably breaks
automake.
Not knowing much about automake (but having despised it for more decades
than I care to admit) I wouldn't be surprised - perhaps I will buy that
book I saw written by someone who understands the guts of it.
Cheers,
Gary B-)
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
