building 4.16 for debian (long)
Michael Tokarev
mjt at tls.msk.ru
Sun Mar 27 11:39:28 UTC 2022
27.03.2022 10:50, Michael Tokarev via samba-technical wrote:
...
> Third, when linking smbd, I'm getting this error:
>
> /usr/bin/ld: source3/smbd/server.c.147.o: in function `notifyd_req':
> ./bin/default/../../source3/smbd/server.c:366: undefined reference to `messaging_ctdb_connection'
>
> apparently source3/lib/messages_ctdb.o is missing somewhere in the link
> line. Maybe this is related to usage of the bundled-libs above.
I fixed this one by the following change:
diff --git a/source3/wscript_build b/source3/wscript_build
index acfc0c56f03..bee623a7347 100644
--- a/source3/wscript_build
+++ b/source3/wscript_build
@@ -1103,6 +1103,7 @@ bld.SAMBA3_BINARY('smbd/smbd',
CMDLINE_S3
smbd_base
REG_FULL
+ samba-cluster-support
''',
install_path='${SBINDIR}')
> --------------------------------------------------
...
> Okay, I moved third_party/heimdal/lib/gssapi/gssapi.h out of the way for now
> to continue, it compiled okay, until failed elsewhere:
>
> In file included from ../../third_party/heimdal/lib/krb5/krb5_locl.h:122,
> from ../../source4/kdc/wdc-samba4.c:31:
> ../../third_party/heimdal/include/crypto-headers.h:5:2: error: #error "need config.h"
>
> Is it because heimdal in samba turned out to be somehow unconfigured
> before being built? Mmmm... Can it be that the samba built system
> found a _system_ heimdal libs and decided it does not need to built it,
> but parts of heimdal sources are used during the build anyway?
..and fixed this one by removing the check for #ifndef PACKAGE_NAME in
third_party/heimdal/include/crypto-headers.h.
After fixing the 5 issues, the build finally finished successfully.
But I'd love to see some explanation as of what's going on there...
Thank you!
/mjt
More information about the samba-technical
mailing list