samba.org::ftp/unpacked/samba_4_0_test/ is broken

[Michael Wood]

On 4 October 2010 10:21, Daniel Müller <mueller at tropenklinik.de> wrote:
> I did it too with source4.
> The same thing!!!
> I also tried a fresh directory syncing the new files. It did not work.

Try adding a --delete to your rsync invocation.  (Although that still
won't work.  See below.)

Also, try leaving out the "make idl_full".

Although, I've just tried it and get the same error:

I've just done:
$ cp -pr src/samba /tmp
$ rsync -avz --delete samba.org::ftp/unpacked/samba_4_0_test/ /tmp/samba/
$ cd /tmp/samba/source4
$ ./autogen.sh

This says to run ./configure or ./configure.developer, so I run
./configure.developer.

$ ./configure.developer
[...]
configure: creating mkconfig.mk

To build Samba, run /usr/bin/make

So I run:
$ make
data.mk:1395: *** commands commence before first target.  Stop.

And indeed there is a data.mk file containing:
################################################
# Autogenerated by source4/build/smb_build/makefile.pm #
################################################
[...]

So, I think samba.org::ftp/unpacked/samba_4_0_test/ is broken.

Also, although it contains a .git directory it points at
/data/git/samba/git/objects in .git/objects/info/alternates, so it
doesn't have all the objects.

Daniel, rather try checking out the source code with git.

hmmm...  I've just realised that using the rsync'ed samba_4_0_test,
configure.developer is the autoconf version and not waf!

/tmp/samba/source4$ ./autogen.sh
Setting up for waf build
done. Now run ./configure or ./configure.developer then make.
/tmp/samba/source4$ ./configure.developer
configure: creating cache config.cache
SAMBA VERSION: 4.0.0alpha14-GIT-355849e
BUILD COMMIT REVISION: 355849ed4cbe5cea86edf6b5414d264c0637ac64
BUILD COMMIT DATE: "Mon Oct 4 08:10:16 2010 +0000"
BUILD COMMIT TIME: 1286179816
BUILD REVISION: 1286179816
LIBREPLACE_LOCATION_CHECKS: START
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
[...]

-- 
Michael Wood <esiotrot at gmail.com>