Statically linking file daemon

Hi!, 

I have the need to build the file daemon statically linked because it
would run in a non-managed by me servers, which would be upgraded (apt
package upgrades) and then the library versions could change, even could
become uninstalled. I run configure as : 

./configure --prefix='/opt/bacula-11.0.5-fd' --enable-client-only
--enable-static --enable-static-fd --disable-libtool --with-openssl
--with-lzo 

When I issue a make I see warnings like : 

/opt/bacula-community-Release-11.0.5/bacula/src/lib/priv.c:76: warning:
Using 'getgrnam' in statically linked applications requires at runtime
the shared libraries from the glibc version used for linking
/usr/bin/ld: ../lib/libbac.a(bsys.o): in function
`get_group_members(char const*, alist*)': 

Can the glibc libraries be copied by some configure flag or option, so
that they to become available for the bacula-fd and I suppose then on
bacula-fd start, that you would have to specify LD_LIBRARY_PATH and
LD_RUN_PATH pointing to that directory where you preserve the glibc
libraries used in the linkage process of building bacula-fd?. 

What's the recommended way to end up by having a static fd without
surprises or problems later?. 

Best regards,

_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel