Re: [Samba] Samba 4 on AIX with XLC
Just to report back in on this, the traditional build system under source3 worked for us, and we were able to build and install a working set of Samba binaries. At this time, we only need the file server bits. I'll give the new build system another shot when 4.0.1 comes out. Thanks again! -Ben -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
On Sat, Jan 12, 2013 at 01:09:55AM +, Benjamin Huntsman wrote: > >Those should have been linked into smbd directly as configure on AIX > >adds vfs_aixacl to the list of modules to be compiled statically. > > > >Would you mind opening a bug on https://bugzilla.samba.org for tracking? > > > >Cheers, > >Christian > > Hi there! >Thanks for the reply! >I have added Bug 9557: https://bugzilla.samba.org/show_bug.cgi?id=9557 > >Any chance it'll be patched by the end of next week? :) har har. > >In the mean time, I think I'm going to revert to trying to build the most > recent stable version of Samba 3.6.x. >I'll happily provide whatever data I can and assist with testing to get > Samba 4 building and running on AIX... Just let me know. Quick remark: if 3.6 is an option for you, then you seem to be happy with just the file server without a DC. For that, the autoconf based build system in source3 should still work the same as it did in 3.6. This will not build the AD DC however. With best regards, Volker Lendecke -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kont...@sernet.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
>Those should have been linked into smbd directly as configure on AIX >adds vfs_aixacl to the list of modules to be compiled statically. > >Would you mind opening a bug on https://bugzilla.samba.org for tracking? > >Cheers, >Christian Hi there! Thanks for the reply! I have added Bug 9557: https://bugzilla.samba.org/show_bug.cgi?id=9557 Any chance it'll be patched by the end of next week? :) har har. In the mean time, I think I'm going to revert to trying to build the most recent stable version of Samba 3.6.x. I'll happily provide whatever data I can and assist with testing to get Samba 4 building and running on AIX... Just let me know. Thanks again! -Ben -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
On 01/11/2013 06:04 PM, Benjamin Huntsman wrote: 1. What can be done about the libraries not getting copied? Is this a bug in my build, or in the build system? I can see this as well on my AIX6.1 system. So it's probably an issue with the build system. 2. Do I need to move certain ones of them to other subdirectories in the lib directory? No, the buildsystem should have copied them there as well. 3. If I tracked down the ones below and copied them by hand, might there be others still that I missed? Once the problem with the buildsystem gets sorted out, you wouldn't have to care. Please open a bug so we can track this problem. 4. With all the subdirectories under lib, am I going to have to define a pretty complicated LD_LIBRARY_PATH to get this to run? No, the binaries should be linked against those libraries with absolute paths. You might only need to set LD_LIBRARY_PATH for libs like libtalloc and libtdb that are supposed to be installed under a standard library path like /usr/lib/. The private libs will be installed somewhere else, but still be found due to the absolute linking. 5. Is there a way I can build the whole thing static from the Python-based build system? I didn't see an option for that with ./configure --help. Not with the waf buildsystem. If you are only interested in the file/print serving part, you can give the old buildsystem in source3 a try instead. Cheers, Christian -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
On 01/10/2013 12:18 AM, Benjamin Huntsman wrote: There may be others, but by copying those into /opt/samba-4.0.0/lib, I was able to get my compiled smbd to at least spit out the following message: bash-3.2# /opt/samba-4.0.0/sbin/smbd -b exec(): 0509-036 Cannot load program /opt/samba-4.0.0/sbin/smbd because of the following errors: rtld: 0712-001 Symbol aixacl_to_smbacl was referenced from module /opt/samba-4.0.0/lib/private/libsmbd_base.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol aixacl_smb_to_aixacl was referenced from module /opt/samba-4.0.0/lib/private/libsmbd_base.so(), but a runtime definition of the symbol was not found. bash-3.2# So looks like I'm still missing aixacl_to_smbacl and aixacl_smb_to_aixacl. Any idea where I'd get those, and why they're not being found? Those should have been linked into smbd directly as configure on AIX adds vfs_aixacl to the list of modules to be compiled statically. Would you mind opening a bug on https://bugzilla.samba.org for tracking? Cheers, Christian -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
Sorry to be an annoyance, but I'm at a loss here and begging for help... The Python-based build says it completes successfully, and the make install also says it completes successfully. Yet it doesn't copy all the required shared libraries, and the resultant binaries don't run. I copied the missing shared objects by hand, which may or may not be a very good solution. I put them all in /opt/samba-4.0.0/lib, but I suspect some of them were intended to live in different subdirectories thereof. Once the named libraries were copied, it then tells me it can't find the following symbols: aixacl_to_smbacl aixacl_smb_to_aixacl Don't know what to do next... So, my questions are: 1. What can be done about the libraries not getting copied? Is this a bug in my build, or in the build system? 2. Do I need to move certain ones of them to other subdirectories in the lib directory? 3. If I tracked down the ones below and copied them by hand, might there be others still that I missed? 4. With all the subdirectories under lib, am I going to have to define a pretty complicated LD_LIBRARY_PATH to get this to run? 5. Is there a way I can build the whole thing static from the Python-based build system? I didn't see an option for that with ./configure --help. Anyway, I think we're crazy close, but I'm still missing that last little hurdle. Many thanks in advance!! -Ben From: samba-boun...@lists.samba.org [samba-boun...@lists.samba.org] on behalf of Benjamin Huntsman [bhunts...@mail2.cu-portland.edu] Sent: Wednesday, January 09, 2013 3:18 PM To: samba@lists.samba.org Subject: Re: [Samba] Samba 4 on AIX with XLC Just FYI, here are at least some of the shared objects that don't get copied to the destination when running "make install": libtalloc.so libgssapi-samba4.so libtdb.so libtevent.so libkrb5-samba4.so libroken-samba4.so libasn1-samba4.so libhcrypto-samba4.so libcom_err-samba4.so libwind-samba4.so libldb.so libheimbase-samba4.so libhx509-samba4.so libpyldb-util.so There may be others, but by copying those into /opt/samba-4.0.0/lib, I was able to get my compiled smbd to at least spit out the following message: bash-3.2# /opt/samba-4.0.0/sbin/smbd -b exec(): 0509-036 Cannot load program /opt/samba-4.0.0/sbin/smbd because of the following errors: rtld: 0712-001 Symbol aixacl_to_smbacl was referenced from module /opt/samba-4.0.0/lib/private/libsmbd_base.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol aixacl_smb_to_aixacl was referenced from module /opt/samba-4.0.0/lib/private/libsmbd_base.so(), but a runtime definition of the symbol was not found. bash-3.2# So looks like I'm still missing aixacl_to_smbacl and aixacl_smb_to_aixacl. Any idea where I'd get those, and why they're not being found? Thanks! -Ben -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
Just FYI, here are at least some of the shared objects that don't get copied to the destination when running "make install": libtalloc.so libgssapi-samba4.so libtdb.so libtevent.so libkrb5-samba4.so libroken-samba4.so libasn1-samba4.so libhcrypto-samba4.so libcom_err-samba4.so libwind-samba4.so libldb.so libheimbase-samba4.so libhx509-samba4.so libpyldb-util.so There may be others, but by copying those into /opt/samba-4.0.0/lib, I was able to get my compiled smbd to at least spit out the following message: bash-3.2# /opt/samba-4.0.0/sbin/smbd -b exec(): 0509-036 Cannot load program /opt/samba-4.0.0/sbin/smbd because of the following errors: rtld: 0712-001 Symbol aixacl_to_smbacl was referenced from module /opt/samba-4.0.0/lib/private/libsmbd_base.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol aixacl_smb_to_aixacl was referenced from module /opt/samba-4.0.0/lib/private/libsmbd_base.so(), but a runtime definition of the symbol was not found. bash-3.2# So looks like I'm still missing aixacl_to_smbacl and aixacl_smb_to_aixacl. Any idea where I'd get those, and why they're not being found? Thanks! -Ben -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
On Tue, Jan 08, 2013 at 07:41:54PM +, Benjamin Huntsman wrote: > >I would ensure gettext is available. That's how it's mostly been > >tested. > > > >Jeremy. > > Hee hee... that worked. Got samba 4 compiled, so, for the record, gettext is > absolutely required. > I also had to use xlC_r (note the capital C) as the > compiler, since XLC will choke on using C++-style comments > in straight C code. Where do we have those comments? I would regard that as a bug in our code. With best regards, Volker Lendecke -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kont...@sernet.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
Also, shouldn't "make clean" delete all the .so's in the build tree? It doesn't. After figuring out that that may be tripping me up, I used 'find . name "*.so" -print | while read so; do rm $so; done' to take care of that. Who knows what other cruft may be lying around though... at this point I may have to just nuke the build tree and re-extract the tarball... Thanks! -Ben -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba 4 on AIX with XLC
Hi again! I'll stop making so much noise shortly, but I've got to get this proved by say, tomorrow, or take a different direction on my project. I got Samba 4 to compile on AIX using the following: # export CFLAGS="-I/opt/openldap-2.4.32/include -qlanglvl=extc99" # CFLAGS="$CFLAGS" ./configure --prefix=/opt/samba-4.0.0 --sysconfdir=/etc/samba-4.0.0 --localstatedir=/var/samba-4.0.0 --with-gettext=/opt/freeware ... # make ... # make install ... # Now unfortunately, while the compile completes, something's not right. If I try to run /opt/samba-4.0.0/sbin/smbd -b, I get the following error: bash-3.2# ./smbd -v exec(): 0509-036 Cannot load program ./smbd because of the following errors: rtld: 0712-001 Symbol aixacl_to_smbacl was referenced from module default/source3/libsmbd_base.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol aixacl_smb_to_aixacl was referenced from module default/source3/libsmbd_base.so(), but a runtime definition of the symbol was not found. bash-3.2# CFLAGS="$CFLAGS" ./configure --prefix=/opt/samba-4.0.0 --sysconfdir=/etc/samba-4.0.0 --localstatedir=/var/samba-4.0.0 --with-gettext=/opt/freeware bash-3.2# echo $CFLAGS -I/opt/openldap-2.4.32/include -qlanglvl=extc99 bash-3.2# What's this aixacl_smb_to_aixacl thing? The last time I built this earlier today, I'd had -qlanglvl=extended set, and was instead tripping up because it couldn't find the symbol va_copy. The following article suggested rebuilding with -qlanglvl=extc99: http://lists.samba.org/archive/samba-technical/2006-October/049777.html After doing so, that's where I get the missing aixacl_to_smbacl problem. Whatever shall I do? There's got to be a way to get the shared libraries installed, and find all the right stuff. On the previous attempt, I just copied all the .so's in place one-at-a-time until it hit the va_copy thing. Many thanks!! -Ben -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
>I would ensure gettext is available. That's how it's mostly been >tested. > >Jeremy. Hee hee... that worked. Got samba 4 compiled, so, for the record, gettext is absolutely required. I also had to use xlC_r (note the capital C) as the compiler, since XLC will choke on using C++-style comments in straight C code. Anyway, thanks again everyone!! -Ben -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
On 8 January 2013 20:46, Benjamin Huntsman wrote: >>See if there's a config.log. Look for things to do with "nls", >>"i18n", "l10n", "gettext" etc. >> >>Btw, I think OpenLDAP and "Active Directory support" are only relevant >>to client/member support for AD. The Samba 4.x AD server has its own >>built-in LDAP and Kerberos components. > > Hi! >There is no config.log, but there is a setting in the ./configure options, > --with-gettext= >So do I need to get gettext? Is it strictly required for Samba 4? > > Many thanks! Try --without-gettext. It should not be required. Sorry I don't have time to try it myself. Also, you might want to try gcc. -- Michael Wood -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
On Tue, Jan 08, 2013 at 06:46:16PM +, Benjamin Huntsman wrote: > >See if there's a config.log. Look for things to do with "nls", > >"i18n", "l10n", "gettext" etc. > > > >Btw, I think OpenLDAP and "Active Directory support" are only relevant > >to client/member support for AD. The Samba 4.x AD server has its own > >built-in LDAP and Kerberos components. > > > >-- > >Michael Wood > > Hi! >There is no config.log, but there is a setting in the ./configure options, > --with-gettext= >So do I need to get gettext? Is it strictly required for Samba 4? I would ensure gettext is available. That's how it's mostly been tested. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
>See if there's a config.log. Look for things to do with "nls", >"i18n", "l10n", "gettext" etc. > >Btw, I think OpenLDAP and "Active Directory support" are only relevant >to client/member support for AD. The Samba 4.x AD server has its own >built-in LDAP and Kerberos components. > >-- >Michael Wood Hi! There is no config.log, but there is a setting in the ./configure options, --with-gettext= So do I need to get gettext? Is it strictly required for Samba 4? Many thanks! -Ben -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
Hi On 8 January 2013 08:57, Benjamin Huntsman wrote: > > >_(...) is how the localisation is done AFAIK. i.e. it's for > >translating messages into different languages. > > > >Maybe there's something wrong with internationalisation/localisation > >(i18n/l10n) on the system? See what the configure output says about > >it (maybe gettext). > > Hi there! >Thanks so much for the response! Very interesting idea. But I'm not sure > what I'd be looking for. Is gettext required? It's almost certainly no > present, as this is a clean build of AIX just for this compile, and I've only > been installing things on an as-needed basis... It shouldn't be required. Haven't compiled Samba in a while, so I don't know the details, but try ./configure --help and see if there's anything to do with nls/i18n/l10n/gettext. Maybe --disable-nls. > How would I check the configure output? See if there's a config.log. Look for things to do with "nls", "i18n", "l10n", "gettext" etc. Btw, I think OpenLDAP and "Active Directory support" are only relevant to client/member support for AD. The Samba 4.x AD server has its own built-in LDAP and Kerberos components. -- Michael Wood -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
>_(...) is how the localisation is done AFAIK. i.e. it's for >translating messages into different languages. > >Maybe there's something wrong with internationalisation/localisation >(i18n/l10n) on the system? See what the configure output says about >it (maybe gettext). > >-- >Michael Wood Hi there! Thanks so much for the response! Very interesting idea. But I'm not sure what I'd be looking for. Is gettext required? It's almost certainly no present, as this is a clean build of AIX just for this compile, and I've only been installing things on an as-needed basis... How would I check the configure output? Many thanks! -Ben -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
Hi
On 8 January 2013 02:16, Benjamin Huntsman
wrote:
>>On Mon, Jan 07, 2013 at 10:58:08PM +, Benjamin Huntsman wrote:
>>> As a further follow-up, here's an example, from source3/utils/net_cache.c:
>>>
>>> d_printf(_("Key: %s\t Timeout: %s\t Value: %s %s\n"), keystr,
>>> timeout_str, datastr, timeout > now_t ? "":
>>> _("(expired)"));
>>>
>>> My C skills aren't good enough to understand what's being done here, but
>>> the offending bit is the last argument to d_printf:
>>>
>>> timeout > now_t ? "": _("(expired)")
[...]
> Any idea how we could track it back to see why that'd be? Did I mess it up
> during the configure, or am I the first person to try to build samba-4.0.0 on
> AIX with XLC?
_(...) is how the localisation is done AFAIK. i.e. it's for
translating messages into different languages.
Maybe there's something wrong with internationalisation/localisation
(i18n/l10n) on the system? See what the configure output says about
it (maybe gettext).
--
Michael Wood
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
>On Mon, Jan 07, 2013 at 10:58:08PM +, Benjamin Huntsman wrote:
>> As a further follow-up, here's an example, from source3/utils/net_cache.c:
>>
>> d_printf(_("Key: %s\t Timeout: %s\t Value: %s %s\n"), keystr,
>> timeout_str, datastr, timeout > now_t ? "": _("(expired)"));
>>
>> My C skills aren't good enough to understand what's being done here, but the
>> offending bit is the last argument to d_printf:
>>
>> timeout > now_t ? "": _("(expired)")
>>
>> Is there a way we can re-write this in more compatible way?
>>
>> Apparently, this construction is supposed to look like:
>>
>> (condition) ? (t_result) : (f_result)
>>
>> and t_result and f_result must be of the same type. So do I read that "" is
>> a char, and _("(expired)") is an int? Something like:
>>
>> timeout > now_t ? atoi(""):_("(expired)") maybe?
>>
>> Again, just grasping here...
>> ... or maybe there's a flag to XLC to let us get by this?
>
>No, both "" and _("(expired)") should evaluate to a const char *.
>
>Looks like the error is that _("") isn't evaluating to a string
>on AIX with xlc.
Hi there! Many many thanks for responding!!
Any idea how we could track it back to see why that'd be? Did I mess it up
during the configure, or am I the first person to try to build samba-4.0.0 on
AIX with XLC?
Thanks!!
-Ben
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
On Mon, Jan 07, 2013 at 10:58:08PM +, Benjamin Huntsman wrote:
> As a further follow-up, here's an example, from source3/utils/net_cache.c:
>
> d_printf(_("Key: %s\t Timeout: %s\t Value: %s %s\n"), keystr,
> timeout_str, datastr, timeout > now_t ? "": _("(expired)"));
>
> My C skills aren't good enough to understand what's being done here, but the
> offending bit is the last argument to d_printf:
>
> timeout > now_t ? "": _("(expired)")
>
> Is there a way we can re-write this in more compatible way?
>
> Apparently, this construction is supposed to look like:
>
> (condition) ? (t_result) : (f_result)
>
> and t_result and f_result must be of the same type. So do I read that "" is
> a char, and _("(expired)") is an int? Something like:
>
> timeout > now_t ? atoi(""):_("(expired)") maybe?
>
> Again, just grasping here...
> ... or maybe there's a flag to XLC to let us get by this?
No, both "" and _("(expired)") should evaluate to a const char *.
Looks like the error is that _("") isn't evaluating to a string
on AIX with xlc.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 on AIX with XLC
As a further follow-up, here's an example, from source3/utils/net_cache.c:
d_printf(_("Key: %s\t Timeout: %s\t Value: %s %s\n"), keystr,
timeout_str, datastr, timeout > now_t ? "": _("(expired)"));
My C skills aren't good enough to understand what's being done here, but the
offending bit is the last argument to d_printf:
timeout > now_t ? "": _("(expired)")
Is there a way we can re-write this in more compatible way?
Apparently, this construction is supposed to look like:
(condition) ? (t_result) : (f_result)
and t_result and f_result must be of the same type. So do I read that "" is a
char, and _("(expired)") is an int? Something like:
timeout > now_t ? atoi(""):_("(expired)") maybe?
Again, just grasping here...
... or maybe there's a flag to XLC to let us get by this?
Many thanks!
-Ben
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba 4 on AIX with XLC
Has anyone tried building Samba 4.0 on AIX with XLC? I'm moving right along, but tripping up on some bugs in source3/utils/net_rpc.c, source3/utils/net_rpc_printer.c, and source3/utils/net_cache.c where there is an invalid use of the ":" operator. According to some other posts on the PostgreSQL forum, this shouldn't compile anywhere, even though GCC apparently allows it?? (http://archives.postgresql.org/pgsql-hackers/1998-09/msg00211.php) Maybe there's a way to skip building these components? Anyway, here's what I'm seeing on the console: bash-3.2# make WAF_MAKE=1 ./buildtools/bin/waf build Waf: Entering directory `/admin/tst/build/samba-4.0.0/bin' Selected embedded Heimdal build [ 8/3655] Generating VERSION [ 44/3655] Generating smbd/build_options.c [2833/3655] Compiling source3/utils/net_rpc.c [2838/3655] Compiling source3/utils/net_cache.c [2844/3655] Compiling source3/utils/net_rpc_printer.c [2851/3655] Compiling source3/utils/net_rpc_shell.c "../source3/utils/net_cache.c", line 87.56: 1506-226 (S) The ":" operator is not allowed between "char[1]" and "int". "../source3/utils/net_cache.c", line 86.18: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_cache.c", line 96.35: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_cache.c", line 184.35: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_cache.c", line 189.26: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_cache.c", line 193.27: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_cache.c", line 216.26: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_cache.c", line 220.27: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_cache.c", line 251.27: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/include/smb_ldap.h", line 69.9: 1506-236 (W) Macro name LDAP_CONST has been redefined. "../source3/include/smb_ldap.h", line 69.9: 1506-358 (I) "LDAP_CONST" is defined on line 50 of /opt/openldap-2.4.32/include/ldap_cdefs.h. "../source3/utils/net_rpc.c", line 88.35: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 281.35: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 389.24: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 446.35: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 482.26: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 487.26: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 539.35: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 546.35: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 559.35: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 565.35: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 580.26: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 582.26: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 583.26: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 585.26: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 586.26: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 587.26: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 645.18: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed. "../source3/utils/net_rpc.c", line 731.34: 1506-280 (W) Function argument assignment between types "const char*" and "int" is not allowed.
