The Samba-Bugzilla – Bug 9077
[4.0 beta5] compile error in pyldb.c: NULL format string
Last modified: 2012-08-11 21:36:34 UTC
Created attachment 7737 [details]
Compiling beta5 and HEAD (master) I get a compile error:
.../lib/ldb/pyldbc.:1833 null format string
config.log and make.log (with waf -vv) are attached.
I don't have ldb installed from ports. But I can't find the error message in the samba source tree, either ...
It worked with beta4.
[How do I attach 2 files at the same time?]
Created attachment 7738 [details]
configure log (zipped)
Same here. Just revert 3aa6f085c22ce33ead23f7ebb604be5525759eee from your checkout and everything is fine.
Should be fixed by 33c79c8731ea0c1ab78583a7c50953c56aea539f
I updated to master today. Now I get the same error (NULL format string) at lib/ldb/ldb_map/ldb_map.c:1018
Since I first 'fixed' this, I realised that a NULL pointer here is a perfectly legitimate (if unusual) use of the API, and so I tried another approach: Only failing other format string errors on compilers that will support a NULL pointer here.
The issue is that the example at the end of bin/config.log and specified in buildtools/wafsamba/samba_autoconf.py succeeds, while the runtime fails.
If you have time, it would be great if you could find me an example that fails at configure time, so I can detect this right.
It might be as simple as testing -Wformat=2 or -Wformat-security at the same time, or something about the C snippet.
Any assistance you can provide here would be most helpful.