Compiled Samba; files in wrong directories
OP deleted content, thread may be of interest to forum members.
Discussion, talk and tips
https://forum.puppylinux.com/
OP deleted content, thread may be of interest to forum members.
Jasper wrote: Mon Jan 08, 2024 10:36 amHi all (Fossapup64-95)
I have had an attempt at compiling Samba and it does provide me with a completed build, however it does not put the files in the correct directories.......... so a little miffed
If I run the application smbstatus from within the build directory it does report the correct build.
These are the steps that I undertook
Downloaded Samba 4.19.3
Downloaded and installed via Python
iso8601
cryptography
pyasn1
Downloaded and installed Parse-Yapp-1.21 (Perl)The build script used is
Code: Select all
./configure --prefix=/usr --enable-selftest --enable-fhs --localstatedir=/var --sysconfdir=/etc --libdir=/usr/${LIBDIR} --includedir=/usr/include --bindir=/usr/bin --sbindir=/usr/sbin -with-configdir=/etc/samba --with-piddir=/var/run --with-privatedir=/etc/samba/private --with-privatelibdir=/usr/${LIBDIR} --with-modulesdir=/usr/${LIBDIR} --with-lockdir=/var/cache/samba --with-logfilebase=/var/log/samba --enable-cups --with-acl-support --with-automount --with-quotas --with-syslog --with-utmp --without-winbind --with-ldap --without-pam --without-ads --without-gpgme --without-ad-dc
I have created a 19mb PET file if anyone wants to look at the contents.
https://www.mediafire.com/file/2x4bno9l ... 3.pet/file
If someone could point out my errors and help me correct them to create a functioning build of Samba, it would be appreciated
where you use ${LIBDIR}. should be lib .
another example if it is a puppy , debian usually goes in /usr/lib/x86_64-linux-gnu
an example I use in devuanpup.
Code: Select all
./configure CFLAGS='-no-pie' CXXFLAGS='-no-pie' --enable-fhs --prefix=/usr --includedir=/usr/include --bindir=/usr/bin --sbindir=/usr/sbin --libdir=/usr/lib/x86_64-linux-gnu --sysconfdir=/etc --localstatedir=/var --with-configdir=/etc/samba --with-piddir=/var/run --with-privatedir=/var/lib/samba/private --with-privatelibdir=/usr/lib/x86_64-linux-gnu --with-modulesdir=/usr/lib/x86_64-linux-gnu --with-lockdir=/var/cache/samba --with-logfilebase=/var/log/samba --enable-cups --with-acl-support --with-automount --with-quotas --with-syslog --with-utmp --with-winbind --with-ldap --with-ads --without-fam --with-experimental-mit-ad-dc --with-pam --with-pammodulesdir=/lib/x86_64-linux-gnu/security --without-systemd
@josejp2424
Thank you for replying to my query and providing me with an explanation/solution.
Looking at your config you include the variable
--with-pam
Is this kernel/OS specific??
Jasper wrote: Mon Jan 29, 2024 5:32 am@josejp2424
Thank you for replying to my query and providing me with an explanation/solution.
Looking at your config you include the variable
--with-pam
Is this kernel/OS specific??
You can use the --without-pam variable.
and the only specific is /x86_64-linux-gnu.
all ubuntu and debian derivatives carry that folder.
slackware arch derivatives do not.
even this setting, CFLAGS='-no-pie' CXXFLAGS='-no-pie' is not necessary to use either, but in my case I use it, because the files that go in bin or sbin are created as binaries.
The only reason I mentioned PAM as is problematic with FP95.
I will try again, thanks again for the input and reply
Failed to build successfully once again
it does not find the folder where the waf file is. when trying to compile json.
make sure you have json installed , and python3-json
Thanks once again for the input
I wil leave it for now.