Am I doing something wrong?
Partially linking bin/mergedobj/dynconfig.o
Partially linking bin/mergedobj/socket_wrapper.o
Partially linking bin/mergedobj/crypto.o
Partially linking bin/mergedobj/talloc.o
Partially linking bin/mergedobj/replace.o
bin/mergedobj/samdb_schema.o: In function `dsdb_module_schema_info_blob_read':
/home/brian/samba-master/source4/dsdb/schema/schema_info_attr.c:146: undefined reference to `dsdb_module_search'
bin/mergedobj/samdb_schema.o: In function `dsdb_module_schema_info_blob_write':
/home/brian/samba-master/source4/dsdb/schema/schema_info_attr.c:242: undefined reference to `dsdb_module_modify'
collect2: ld returned 1 exit status
make: *** [bin/regpatch] Error 1
Are you still using the old gmake-based build system? I would strongly suggest to use WAF from now on - which checks better for dependencies and has far less issues.
Start it on a clean tree (on GIT: "git clean -d -f -x ." under the repo dir) using "./autogen-waf.sh", "./configure", "make".
It should fix the problem. Please answer if it does or does not.
That looks a lot better. I had been blindly following the instructions at http://wiki.samba.org/index.php/Samba4/HOWTO without realizing there was a new build system.
the autoconf based build is still the default and should always at least compile!
Doing a complete clean build should fix the problem with both build systems.
Just to clarify, my failed build attempts against the old build system were against a clean source tree, and on different days each using the latest git source.
What is your software environment (OS, C compiler release, platform...)?
This was an up-to-date Debian squeeze system. I used the compilers, etc, from Debian Squeeze.
Well, now it is clear that the WAF build is the default for s4. So please use it! The old autoconf-based bs could be dropped soon.
Matthias, please verify that this is actually fixed. We still support the autoconf-based system.
Jelmer, I was told by abartlet or tridge that the s4 autoconf build shouldn't be maintained anymore since it could be dropped out in the next time.
If you represent another opinion I would like to invite you to post this clearly on the mailing list. I think there is really an uncertainty - as you may have noticed the most time the old build is down.
It will be dropped in the future, but for the time being it's still there. If we weren't maintaining it anymore we would've removed it.
Regarding the old build system: we had some discussion about how to maintain it since there are some dissensions. Probably it will remain for configuration testing ("./configure" outputs and comparisons with the new system) - so no regular maintenance is planned.
We encourage people to use the WAF system as we do. It is faster, generates smaller binaries and it is easier to maintain.
Therefore marking this as "WONTFIX".