On Fri, September 23, 2011 4:02 pm, Martin Simmons wrote: >>>>>> On Fri, 23 Sep 2011 10:34:51 -0400, Kim Culhan said:
>> Compiling bacula here does not produce libbac.so > > Ah, that's one reason why you don't get the same warnings as the OP! I see > now that you are passing --disable-libtool, which will change things a little. > > OTOH, I would still expect the warning when linking bacula-dir. What is the > output of the elfdump on that? i.e. > > elfdump -s bacula-dir | grep plugin Output is attached As noted in a previous message, with a correct libtool it now produces those warnings but not when compiling with --disable-libtool. -kim
elfdump_bacula-dir.out
Description: Binary data
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
