Samba 4 build system (was: Re: Samba3 build farm can't execute smbtorture4 anymore)

Andrew Bartlett abartlet at
Tue Dec 25 21:51:02 GMT 2007

On Mon, 2007-12-24 at 08:59 +0100, Volker Lendecke wrote:

> It does work, and thanks to metze (I think..) the build farm
> runs samba4 torture again for samba3. The problem I have
> with LD_LIBRARY_PATH is that I have multiple installations
> on my disk here, and with having to depend on shared libs I
> am not able to just call this or that instance without
> correctly configuring LD_LIBRARY_PATH. The alternative would
> be to make that a relative path, but then I would have to cd
> into the correct directory always.
> There are always solutions to work with shared libs, but
> when debugging stuff I know at some point I will get stuff
> wrong and run against the wrong library. For libraries that
> are either trivially simple (i.e. libwbclient) or mature
> enough to only change very infrequently (i.e. libc or for
> example talloc) this is ok even on a development machine,
> but anything that still sees considerable change (and I
> would consider ldb in that category) this is just a huge
> pain. IMO it falls into the same category as the Samba4
> single process mode. Everything in one place is far easier
> to debug than everything spread around.

I was trying to express this on IRC a few days ago, but this puts my
position very well. 

My only thought was to link up one set of binaries with -rpath, and use
these for all debugging (but never put them into RPMs
or /usr/local/samba). 

Andrew Bartlett

Andrew Bartlett                      
Authentication Developer, Samba Team 
Samba Developer, Red Hat Inc.        

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :

More information about the samba-technical mailing list