similar to: waf workaround?

21 jun 2014 the version numbers changed (samba-4.1.8), but the problem remains exactly the same: waf configure continues to break at krb5. frank smith 31 may 2014 greetings, in the (relatively distant) past, i several times downloaded, built, and ran the then-current version of samba with little to no problem. i recently experienced similar successful results with samba-3.6.23. i

(This is the Team's agreed statement explaining the role of the two build systems in Samba 4.0. Please, if you have can't use the waf build system, and so need the autoconf system for 4.0, reply and let us know your reasons and needs here or in the specific threads I'm raising on samba-technical). Thanks, Andrew Bartlett BUILDING SAMBA 4.0 (which build system to use and why)

I am working on migrating the RHEL/CentOS Samba 4 rpm to 4.1.12. I noticed that it is no longer building tdbbackup, but it was a few hours ago before other (unknown) environment/config changes. So I started digging through the build system to see how it is enable/disabled. http://wiki.samba.org/index.php/Waf Does not tell me what causes waf to build in lib/tdb/ A little navigation help would

Hi all, As samba4 git source took a looong time to download, I've moved the folder away from original directory. Trying to compile 4.0.10, make shows : > 'configure' finished successfully (52.943s) > WAF_MAKE=1 python ./buildtools/bin/waf build > cannot find include/config.h > Waf: Entering directory `/home/serveur/git/samba4/bin' > bld.curdir >

31 may 2014 greetings, in the (relatively distant) past, i several times downloaded, built, and ran the then-current version of samba with little to no problem. i recently experienced similar successful results with samba-3.6.23. i downloaded and tried to configure samba-4.1.7, which you (samba) advertise as the current "stable" version. i expected no problems. unfortunately, i

All going fine with new RC1, however one suggestion I would make for the new configure scripts which are much more helpful than the old style ones, would be to put more of a warning about ACL support being needed to successfully provision an domain - or make it a configure failure if this is not found? Maybe with an option to pass to configure to allow overriding the error??? . I was aware

Dear all, trying to build some Heimdal-based packages for Samba AD DC under openSUSE I am facing some difficulties with the build system: During the installation which is triggered by "make install" waf complains about some task dependency cycle after leaving folder bin/default. Full log including config options can be seen unter https://build.opensuse.org/

Hi, I'm trying to build Samba from source on a RHEL version 8 server. I installed all the necessary packages and untarred the source for Samba version 4.6.10. In the past I have been able to successfully build and install Samba version 4.13.17 on a RHEL version 7 server with Python2. Here I believe I am using Python3, but I cannot seem to get past the configure command: [root at v2ecsqapp09

I don't think you are going to have much luck getting 4.17 working on CentOS 7. We recently moved from CentOS 7 (4.13) to Rocky Linux 8 (4.16) and the install process was much easier. On Wed, Jan 18, 2023 at 12:03 PM Greg Dickie via samba < samba at lists.samba.org> wrote: > Ok now, but did 4.10.16? I was just trying to rebuild their source RPM. > > Trying 4.17 on the command

Ok now, but did 4.10.16? I was just trying to rebuild their source RPM. Trying 4.17 on the command line (with python3) gives me: > [root at srvlxfs2 samba-4.17.4]# ./configure > Setting top to : > /root/rpmbuild/BUILD/samba-4.17.4 > Setting out to : > /root/rpmbuild/BUILD/samba-4.17.4/bin > Checking for 'gcc' (C

​No, sorry, it's actually failing on "configure" which this script calls. I should have been more clear. ./configured is failing at step: ​*Checking uname sysname type* It's obviously missing some app/header/library, but reading through all the breakpoints listed in the error (re-pasted below) I can't make out from the code what it's looking for, and the config.log

I am trying to build Samba 4.6.4 on an ARM 7 Cortex based router (Netgear R8000), running *DD-WRT v3.0-r31980M kongac (05/11/17)* I'm working with some folks via the DDWRT, but we're running into an issue trying to build from source. I have python 2.7 already installed on the router, and I'm executing the install_with_python.sh script. ./install_with_python.sh /opt/test/samba-4.6.4

I'm currently using Samba 2.2.5 on a Mandrake 8.0 box with cups 1.1.4. I have several printers shared that are accessed from winNT/2k/xp boxes. When I right click on the printer or select printer properties, or go to print from any of those other boxes, the response is slower than molasses. I have an identical machine running WinNT Workstation that was previously our print server. It is

Am Sonntag, 14. Juli 2019, 22:10:10 CEST schrieb Johannes Engel: > Dear all, > > trying to build some Heimdal-based packages for Samba AD DC under > openSUSE I am facing some difficulties with the build system: > During the installation which is triggered by "make install" waf complains > about some task dependency cycle after leaving folder bin/default. > Full log

Dear Samba experts, I tried to install the latest Samba release the way I did it always, i.e. starting with: ./configure --prefix=/usr/local/samba \ --with-piddir=/usr/local/samba/var/run \ --with-syslog \ --with-quotas \ --with-acl-support \ --enable-debug \ --enable-cups \ --enable-selftest \

Hello all: I am trying to build smbtorture using static linked libraries. The samba source code I have is samba-4.1.13 for configure, I did: waf configure --builtin-libraries=ALL for build, I did: waf build --targets=smbtorture (so that it only build target smbtorture) But, the waf build fails immediately. Then, I tried to only link with lib talloc and tevent statically, so I did: waf

I'm doing some work trying to build SRPM's for samba-4.0.2 on Fedoar 18, to update from the 4.0.0rc5 currently available for it. and maybe even to backport to RHEL 6. Unfortunately, even the original and unmodified SRPM from Red Hat fails to build because the "buildtools/bin/waf" is *spewing* temporary files into /tmp/wfcache. /tmp is mounted as a "tmpfs" filesystem,

I am unable to compile Samba 4.4.7, 4.5.1 or 4.5.3 on Solaris 11. I had been able in the past so maybe an update to GCC broke something. GCC 4.8 is the default. I then installed GCC 4.9. /usr/bin/gcc is a symlink to /usr/gcc/4.9/bin/gcc. I compiled the latest openldap (client only) to the samba target directory. Set environmental variables so the krb5.h and openldap would be found.

Hello all: I am trying to build smbtorture using static linked libraries. The samba source code I have is samba-4.1.13 for configure, I did: waf configure --builtin-libraries=ALL for build, I did: waf build --targets=smbtorture (so that it only build target smbtorture) But, the waf build fails immediately. Then, I tried to only link with lib talloc and tevent statically, so I did: waf

I can compile Samba4 beta 4, but can't install it: root at samba4dc:/usr/src/samba-4.0.0beta4# ./configure.developer <snip> 'configure' finished successfully (49.871s) root at samba4dc:/usr/src/samba-4.0.0beta4# make WAF_MAKE=1 ./buildtools/bin/waf build <snip> Waf: Leaving directory `/usr/src/samba-4.0.0beta4/bin' 'build' finished successfully