Bug 8782 - Cannot link with libsmbconf.so.0?
Summary: Cannot link with libsmbconf.so.0?
Status: RESOLVED INVALID
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: Build (show other bugs)
Version: unspecified
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Andrew Tridgell
QA Contact: samba4-qa@samba.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-27 17:35 UTC by Milan Crha
Modified: 2012-03-20 16:09 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Crha 2012-02-27 17:35:15 UTC
I just updated openchange, its trunk at revision 3727, and it fails to build with an error:

   $PREFIX/samba/lib/libsmbconf.so.0: undefined reference
   to `hash_any@SAMBA_4.0.0ALPHA18'

when linking some of its binaries. This wasn't a problem with alpha17, though openchange had many other changes landed between these two too.

Looking around I found 'hash_any' in samba4/lib/ccan/hash/hash.c, and the libsmbconf.so.0 has this library in a list of libraries, because:

   $ ldd $PREFIX/samba/lib/libsmbconf.so.0 | grep ccan

returns
   libccan.so.0 => $PREFIX/samba/lib/private/libccan.so.0 (0x00007fccd120e000)

Do you know what can be wrong when ldd can find the library, please?
Comment 1 Milan Crha 2012-02-27 17:37:59 UTC
Note this fails even when I add 

   $PREFIX/samba/lib/private

into my /etc/ld.so.conf.d/samba4.conf and run ldconfig as root
Comment 2 Matthias Dieter Wallnöfer 2012-02-27 17:56:37 UTC
Rusty, could you help us please?
Comment 3 Milan Crha 2012-02-28 11:47:44 UTC
There is a temporary patch to samba3 sources here [1], if it'll help to fix it properly, though I guess you are aware of this already. The change works for me.

[1] http://mailman.openchange.org/pipermail/devel/2012-February/005447.html
Comment 4 Milan Crha 2012-03-20 16:09:45 UTC
I guess we can mark this as invalid. Using stock samba4 build works as expected, only my local build resists from being a good piece of software. Probably something locally related.

Jelmer also suggested to add ccan dependency into the build script, but it didn't help me. (It was quite confusing, because it seemed it did help, but when I rebuilt again then it failed.)

I'll reopen in case I'll face of this any time later, with the stock samba4 build.