Running master/Samba3 fails because of system talloc

[simo]

On Tue, 2009-03-24 at 23:15 +1100, Andrew Bartlett wrote:
> On Tue, 2009-03-24 at 08:10 -0400, simo wrote:
> > On Tue, 2009-03-24 at 20:57 +1100, Andrew Bartlett wrote:
> > > I've just built Samba3 from master, and have found that, because I have
> > > libtalloc on my system, it prefers to link against this (and fail to
> > > run), than to use the copy Samba3 built.
> > > 
> > > bin/smbclient
> > > bin/smbclient: symbol lookup error: bin/smbclient: undefined symbol:
> > > _talloc_get_type_abort
> > 
> > We just need to make sure samba3 checks for the right version being
> > available when we build it. If samba3 depends on 1.2.1 and does not
> > check for it, then it is just a configure error.
> 
> It checks for libtalloc, determines it must build it's own (as a .so),

This is the bug in configure.
If talloc is installed but it is the wrong version you either build with
talloc compiled statically or (preferably) by default you error out.

> but then includes -ltalloc on the gcc line.  Because the libtalloc it
> built isn't installed yet (and not in a default search path anyway), it
> tries to use the system one.

Bad move indeed.

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer <simo at samba.org>
Principal Software Engineer at Red Hat, Inc. <simo at redhat.com>