On Wed, 2022-01-05 at 12:41 -0500, Leo C via samba wrote:> Hi, > > ./configure --enable-fhs --prefix=/usr --sbindir=/usr/sbin > --bindir=/usr/bin --sysconfdir=/etc --localstatedir=/srv/samba > --mandir=/usr/share/man --enable-debug --enable-selftest --cross- > answers > --enable-cups --with-shared-modules='!vfs_snapper' --with-system- > mitkrb5 > --with-experimental-mit-ad-dc > > I want to compile samba 4.15.3 and it gives me the following error > > ERROR: The MIT KRB5 build with Samba AD requires at least 1.19. > 1.18.3 has > been found and cannot be used > ERROR: If you want to just build Samba FS (File Server) use the > option > --without-ad-dc which requires version 1.9 > ERROR: You may try to build with embedded Heimdal Kerberos by not > specifying --with-system-mitkrb5 > > I'm using debian 11 > > missing? what I'm doing wrong? > installed all necessary packagesYou are going to have to use the krb5 packages from experimental. The question has to be, why do you need to build Samba with MIT instead of Heimdal ? If you just want the latest Samba, see here: https://apt.van-belle.nl/ Rowland
You are right, it is experimental thanks El mi?, 5 ene 2022 a las 13:20, Rowland Penny via samba (< samba at lists.samba.org>) escribi?:> On Wed, 2022-01-05 at 12:41 -0500, Leo C via samba wrote: > > Hi, > > > > ./configure --enable-fhs --prefix=/usr --sbindir=/usr/sbin > > --bindir=/usr/bin --sysconfdir=/etc --localstatedir=/srv/samba > > --mandir=/usr/share/man --enable-debug --enable-selftest --cross- > > answers > > --enable-cups --with-shared-modules='!vfs_snapper' --with-system- > > mitkrb5 > > --with-experimental-mit-ad-dc > > > > I want to compile samba 4.15.3 and it gives me the following error > > > > ERROR: The MIT KRB5 build with Samba AD requires at least 1.19. > > 1.18.3 has > > been found and cannot be used > > ERROR: If you want to just build Samba FS (File Server) use the > > option > > --without-ad-dc which requires version 1.9 > > ERROR: You may try to build with embedded Heimdal Kerberos by not > > specifying --with-system-mitkrb5 > > > > I'm using debian 11 > > > > missing? what I'm doing wrong? > > installed all necessary packages > > You are going to have to use the krb5 packages from experimental. > The question has to be, why do you need to build Samba with MIT instead > of Heimdal ? > If you just want the latest Samba, see here: > https://apt.van-belle.nl/ > > Rowland > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
On Wed, Jan 5, 2022 at 1:20 PM Rowland Penny via samba <samba at lists.samba.org> wrote:> > On Wed, 2022-01-05 at 12:41 -0500, Leo C via samba wrote: > > Hi, > > > > ./configure --enable-fhs --prefix=/usr --sbindir=/usr/sbin > > --bindir=/usr/bin --sysconfdir=/etc --localstatedir=/srv/samba > > --mandir=/usr/share/man --enable-debug --enable-selftest --cross- > > answers > > --enable-cups --with-shared-modules='!vfs_snapper' --with-system- > > mitkrb5 > > --with-experimental-mit-ad-dc > > > > I want to compile samba 4.15.3 and it gives me the following error > > > > ERROR: The MIT KRB5 build with Samba AD requires at least 1.19. > > 1.18.3 has > > been found and cannot be used > > ERROR: If you want to just build Samba FS (File Server) use the > > option > > --without-ad-dc which requires version 1.9 > > ERROR: You may try to build with embedded Heimdal Kerberos by not > > specifying --with-system-mitkrb5 > > > > I'm using debian 11 > > > > missing? what I'm doing wrong? > > installed all necessary packages > > You are going to have to use the krb5 packages from experimental. > The question has to be, why do you need to build Samba with MIT instead > of Heimdal ? > If you just want the latest Samba, see here: > https://apt.van-belle.nl/ > > RowlandRHEL 7 and matching releases are in a similar state: they can't use the default krb5-libs nor can they build up the Heimdal based libraries without providing a newer gnutls. Given that RHEL 7 only has 2 years of support left, I'm ready to throw in the towel on trying to maintain domain controller enabled backports for it.