On Fedora 13 (and apparently Fedora 14), the linker complains about not being able to find a symbol: data_blob_named
That is present in the public headers, and a private library (samba/libsamba-util-common), but not in public library.
The problem doesn't appear to occur on Ubuntu 10.04 / 10.10 boxes, so there is possibly a linker difference.
Brad, do you speak about linking afterwards against the shared objects generated by the s4 build system?
Since on the normal s4 (developer) build on Fedora 13 I have no problem at all.
Matthias, this bug is about the installed libraries, not the build process to create them.
Brad, has this already been worked on? I mean, did the header changes improve the situation?
Its still a problem.
I don't think the header changes could possibly have affected this, since its a library / linker issue.
(In reply to comment #4)
> Its still a problem.
> I don't think the header changes could possibly have affected this, since its a
> library / linker issue.
s4 should be linking all libraries with the -Wl,-no-undefined flag, which should
mean that all libraries have all symbols resolved, or the creation of the library will fail.
Can you check if that flag is indeed being used? Make with V=1 should show you the build flags.
Hi Brad, in order to properly build in Fedora, it seem that for now you need to uncomment a snippet of code in config.mk.in to explicitly include libsamba-util-common.so on the linker line.
This is because of: https://fedoraproject.org/wiki/UnderstandingDSOLinkChange
I think we need to move these dependencies to a public library of course, but for now that's a reasonable workaround until we iron this out.
Brad, can you check that commit 5d55ae0a2907b5ead5fb7d131aa00788d806ed9a fixes the problem for you ?
As discussed on IRC, it appears additional changes are required.
This problem has also been reported against Debian Sid as of 28 March 2011.
Brad, did this commit fix your problem? http://gitweb.samba.org/samba.git/?p=samba.git;a=commitdiff;h=2c55a995fef133c1854058ed5de83185b9325895
It is ugly (more workaround than correct fix), so not sure if there should be a longer term bug / tracking item to remove it when the shared build stuff is complete. However it resolves the issue for OpenChange.
I'm happy for this to be closed now.