emerge stops before configure with: CCFLAGS="-O2 -pipe -march=native -mtune=native" LINKFLAGS="-O2 -pipe -march=native -mtune=native -Wl,-O1 -Wl,--as-needed" "/ebuild/working/portage/net-fs/samba-4.2.4-r1/work/samba-4.2.4/buildtools/bin/waf" --prefix=/usr --libdir=/usr/lib64 --enable-fhs --sysconfdir=/etc --localstatedir=/var --with-modulesdir=/usr/lib64/samba --with-piddir=/var/run/samba --bundled-libraries=NONE --builtin-libraries=NONE --disable-rpath --disable-rpath-install --nopyc --nopyo --with-acl-support --without-ad-dc --with-dnsupdate --with-ads --with-shared-modules=idmap_ad --with-aio-support --with-ctdb-dir=/usr --enable-avahi --with-cluster-support --enable-cups --without-dmapi --with-fam --enable-gnutls --disable-iprint --with-ldap --with-pam --with-pam_smbpass --with-pammodulesdir=/lib64/security --with-quotas --with-syslog --with-systemd --with-winbind configure waf [command] [options] Main commands (example: ./waf build -j4) build : build all targets clean : removes the build files configure : configures the project ctags : build 'tags' file using ctags dist : makes a tarball for distribution distcheck : test that distribution tarball builds and installs distclean : removes the build directory etags : build TAGS file using etags install : installs the build files pep8 : run pep8 validator pydoctor : build python apidocs reconfigure : reconfigure if config scripts have changed test : Run the test suite (see test options below) testonly : run tests without doing a build first uninstall : removes the installed files wafdocs : build wafsamba apidocs wildcard_cmd: called on a unknown command waf: error: no such option: --with-ctdb-dir Reproducible: Always Steps to Reproduce: 1. USE="cluster" emerge =net-fs/samba-4.2.4-r1 2. 3. Actual Results: stopped emerge Expected Results: correct build
Please attach the full build log and add emerge --info.
Created attachment 412914 [details] build.log
Created attachment 412916 [details] emerge --info
(In reply to alexander haensch from comment #0) > waf: error: no such option: --with-ctdb-dir --- /usr/portage/net-fs/samba/samba-4.2.5.ebuild 2015-10-28 08:31:02.000000000 +0000 +++ /usr/portage/local/layman/blah/net-fs/samba/samba-4.2.5.ebuild 2015-10-30 12:27:45.685184290 +0000 @@ -51,7 +51,6 @@ acl? ( virtual/acl ) addns? ( net-dns/bind-tools[gssapi] ) aio? ( dev-libs/libaio ) - cluster? ( >=dev-db/ctdb-1.0.114_p1 ) cups? ( net-print/cups ) dmapi? ( sys-apps/dmapi ) fam? ( virtual/fam ) @@ -128,7 +127,7 @@ $(use_with ads) $(usex ads '--with-shared-modules=idmap_ad' '') $(use_with aio aio-support) - $(usex cluster '--with-ctdb-dir=/usr' '') + $(usex cluster '--with-cluster-support' '') $(use_enable avahi) $(use_with cluster cluster-support) $(use_enable cups) Can't remember now where I found it, but IIRC ctdb/cluster stuff is bundled now. * Detected file collision(s): * * /usr/bin/ctdb_diagnostics * /usr/bin/smnotify * /usr/bin/onnode * /usr/bin/ctdb * /usr/bin/ping_pong * /usr/bin/ltdbtool * /usr/sbin/ctdbd * /usr/share/man/man1/onnode.1.bz2 * /usr/share/man/man1/ping_pong.1.bz2 * /usr/share/man/man1/ctdbd.1.bz2 * /usr/share/man/man1/ltdbtool.1.bz2 * /usr/share/man/man1/ctdb.1.bz2 * /usr/lib64/pkgconfig/ctdb.pc * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * net-fs/samba-4.2.4-r1:0::comodo * /usr/bin/ctdb * /usr/bin/ctdb_diagnostics * /usr/bin/ltdbtool * /usr/bin/onnode * /usr/bin/ping_pong * /usr/bin/smnotify * /usr/lib64/pkgconfig/ctdb.pc * /usr/sbin/ctdbd * /usr/share/man/man1/ctdb.1.bz2 * /usr/share/man/man1/ctdbd.1.bz2 * /usr/share/man/man1/ltdbtool.1.bz2 * /usr/share/man/man1/onnode.1.bz2 * /usr/share/man/man1/ping_pong.1.bz2 * * Package 'dev-db/ctdb-1.13-r1' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message.
4.2.7 and now 4.2.7-r1 have gone stable with the same issue.
(In reply to Mike Williams from comment #5) > 4.2.7 and now 4.2.7-r1 have gone stable with the same issue. There's still no samba-4 version marked stable on any arch. I suppose you mean the bug being reported here still isn't fixed yet?
This has been fixed in samba-4.2.7-r2 and samba-4.3.4-r1
