|
On Mon, September 26, 2011 10:29 am, Martin Simmons wrote:
>>>>>> On Fri, 23 Sep 2011 17:16:31 -0400, Kim Culhan said:
>> As noted in a previous message, with a correct libtool it now produces
>> those warnings but
>> not when compiling with --disable-libtool.
>
> OK.
>
> However, I would expect ld to give a warning when linking bacula-dir without
> --disable-libtool too, because it also defines plugin_list globally.
Yes ld gives the 'plugin_list' warning without --disable-libtool, with --disable-libtool
it does not give those warnings and produces working bacula files.
With --disable-libtool there are some warnings of the general type:
Compiling crypto.c
"crypto.c", line 567: Warning (Anachronism): Formal argument cb of type extern "C" int(*)(char*,int,int,void*) in call to PEM_read_bio_PrivateKey(bio_st*, evp_pkey_st**, extern "C" int(*)(char*,int,int,void*), void*) is being passed int(*)(char*,int,int,void*)
-kim
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
| 