X-Git-Url: http://git.samba.org/samba.git/?p=sfrench%2Fsamba-autobuild%2F.git;a=blobdiff_plain;f=BUILD_SYSTEMS.txt;h=f1d1ce393fb7111e02d362b64da3281dd0861039;hp=f8590f6375ad6441e220536bc7f592e210476102;hb=0ed6ad45ad4dd8deda2d86157bba27ebb13225f0;hpb=3787dcf42c9ab9ec5a3648b14f86e8bb2032958e

diff --git a/BUILD_SYSTEMS.txt b/BUILD_SYSTEMS.txt
index f8590f6375a..f1d1ce393fb 100644
--- a/BUILD_SYSTEMS.txt
+++ b/BUILD_SYSTEMS.txt
@@ -1,5 +1,4 @@
 BUILDING SAMBA 4.0
-(which build system to use and why)
 ===================================
 
 The waf build
@@ -59,38 +58,23 @@ our users, for whatever purpose you want to put Samba to.
 The autoconf build
 ------------------
 
-For a small number of users, the requirement to have access to Python
-2.4 and perl will be unacceptable, and for these users we continue to
-provide the 'autoconf' build system used in Samba 3.x under the
-source3/.  This will build fewer parts of Samba, but should not be seen
-as 'the file server build' (typical file server deployments should use
-the top level build), but as a measure provided with limited features
-for systems and organisations unable to meet the requirements for the
-new build system.
-
-If you do need to use the autoconf build system, please let us know:
-both why you cannot use the 'waf' build in the top level, and what
-features of the source3 build that you require.  We need this
-information to assess the continuing demand for this parallel
-infrastructure, and to determine which features need to remain available
-in both build systems.
+The autoconf build was removed in Samba 4.1.  If you have tried and
+failed to use our waf build system, you may wish to use the latest
+supported 4.0 release instead, while we address your use case.
 
 Optional Libraries
 ------------------
 
 To assist users and distributors to build Samba with the full feature
-set, by the first release candidate the build system will abort if our
-dependent libraries and their header files are not found on the target
-system.  This will mean for example, that xattr, acl and ldap headers
-must be installed for the default build to complete.  The configure
-system will check for these headers, and the error message will
-indicate:
- - the required header and library
- - the option (such as --without-acl-support) that can be specified to
-   skip this requirement, and
- - the feature (ACL support optional for file servers, mandatory for AD
-   Domain Controller) being skipped. 
+set, the build system will abort if our dependent libraries and their
+header files are not found on the target system.  This will mean for
+example, that xattr, acl and ldap headers must be installed for the
+default build to complete.  The configure system will check for these
+headers, and the error message will indicate the option (such as
+--without-acl-support) that can be specified to skip this requirement.
 
 This will assist users and in particular distributors in building fully
 functional packages, while allowing those on systems truly without these
-facilities to continue to build Samba after careful consideration. 
+facilities to continue to build Samba after careful consideration.
+
+This feature is not currently supported for xattr.