Created attachment 547 [details]
Suggested patch

jelmer, please look at this patch and apply if you think it is ok.
we need to close out some of the long standing issues.  Thanks.

Patch applied. Thanks for your feedback! (and thanks to Jerry for noticing me of this bugzilla entry) 

Jelmer, I had to revert the fix because too many dependencies are created
(noticed while rpm-packaging). 

This way rpcclient (and thus samba3-client.rpm) always requires too many libs
(mysql, postgres, libxml) as soon as once decides to build the pdb-modules as well.

Guenther,

the Makefile.in fix is OK, but @XML_LIBS@, @MYSQL_LIBS@ and @PGSQL_LIBS@ must
not be defined unless you intend to link against these libraries.

It is not possible to handle that in Makefile.in, it requires some additional
configuration work in configure (don't define @*_LIB@ if it is not required).

Linking statically against something means that all symbols used must be
resolvable - without exceptions. If you live in a pure shared library
environment, unresolved symbols don't necessarily become visible.

There is a couple of places in Samba (see bug #1641, for example) where this
under certain (rather rare) circumstances becomes a problem.

My personal experience is: If static linking works, dynamic linking will also
work. If dynamic linking works, static linking will not necessarily work.

I understand that there is a whole lot of different configurations and OS
flavors and that satisfying the respective requirements results in a whole lot
of work and extensive testing. I really do appreciate the fact that there are
people out there who voluntarily do this without direct economic interests!

Cheers,
Max

*** Bug 1641 has been marked as a duplicate of this bug. ***

Exactly what errors do you get when linking rpcclient?

no feedback in over a month.

expsam is no longer part of the samba code base

reopen

expsam is no longer part of the samba code base