Bug 5723 - libwbclient can't be linked statically
Summary: libwbclient can't be linked statically
Alias: None
Product: Samba 3.2
Classification: Unclassified
Component: Build environment (show other bugs)
Version: unspecified
Hardware: x86 Linux
: P3 normal
Target Milestone: ---
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
Depends on:
Reported: 2008-08-28 07:52 UTC by Gabor Z. Papp
Modified: 2008-08-28 09:21 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Gabor Z. Papp 2008-08-28 07:52:36 UTC
Since the new 3.2.x releases
can't link libwbclient statically to the binaries.

$ ldd ./bin/net 
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x4001e000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x4004c000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x4005f000)
        libdl.so.2 => /lib/libdl.so.2 (0x40074000)
        libreadline.so.5 => /pkg/lib/libreadline.so.5 (0x40078000)
        libncurses.so.5 => /pkg/lib/libncurses.so.5 (0x400a5000)
        libwbclient.so.0 => /pkg/lib/libwbclient.so.0 (0x400e7000)
        libc.so.6 => /lib/libc.so.6 (0x400f0000)
        /lib/ld-linux.so.2 (0x40000000)
        libtalloc.so.1 => /pkg/lib/libtalloc.so.1 (0x40207000)

Modifiying the source/Makefile, and replacing libwbclient.so with libwbclient.a solved the problem till 3.2.1, but since 3.2.2 this trick does not works any more.
Comment 1 Gerald (Jerry) Carter (dead mail address) 2008-08-28 09:21:35 UTC
The entire point of libwbclient is to provide a shared lib interface between smbd
(and other applications) and winbindd.  Allowing a static link just recouples the two.