Summary: | net-fs/samba-4.16.0: third_party/heimdal/kdc/kdc-private.h:224:9: error: unknown type name ‘gss_OID_set’ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Erik Zeek <zeekec> |
Component: | Current packages | Assignee: | Gentoo's SAMBA Team <samba> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gentoo, jstein, marien.zwart, ole+gentoo, phantom4, programming, rzubaly, sam, voron1 |
Priority: | Normal | Keywords: | PATCH |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://lists.samba.org/archive/samba-technical/2022-May/137349.html | ||
See Also: | https://bugs.debian.org/1013205 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 351559 | ||
Attachments: | build log |
Description
Erik Zeek
2022-03-26 14:27:05 UTC
> emerge -pqv '=net-fs/samba-4.16.0::gentoo'
[ebuild U ] net-fs/samba-4.16.0 [4.15.6] USE="client cups json pam python quota regedit syslog systemd winbind zeroconf -acl -addc -ads -ceph -cluster -debug (-fam) -glusterfs -gpg -iprint -ldap -profiling-data (-selinux) -snapper -spotlight (-system-heimdal) -system-mitkrb5 (-test)" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="aes" PYTHON_SINGLE_TARGET="python3_9 -python3_8 -python3_10"
I felt on a similar problem yesterday when compiling this package and found a missing dependency. That is new but samba 4.16 have a build dependency on dev-perl/JSON I was struggling with updating samba as well, until I saw this. I have USE=-json set, but it seems that samba requires dev-perl/JSON anyway, even with the use flag disabled. However samba does not pull in the dep automatically. After emerging dev-perl/JSON, net-fs/samba-4.16 was able to emerge successfully. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=093c4cde84466c321d4f7b61210d51a302c7906e commit 093c4cde84466c321d4f7b61210d51a302c7906e Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2022-03-28 19:31:12 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2022-03-28 19:31:34 +0000 net-fs/samba: Added dev-perl/JSON to DEPEND Bug: https://bugs.gentoo.org/836167 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> net-fs/samba/samba-4.16.0.ebuild | 1 + 1 file changed, 1 insertion(+) It is only strictly required for samba[addc], and is optional otherwise. (In reply to Larry the Git Cow from comment #4) > The bug has been referenced in the following commit(s): > > https://gitweb.gentoo.org/repo/gentoo.git/commit/ > ?id=093c4cde84466c321d4f7b61210d51a302c7906e > > commit 093c4cde84466c321d4f7b61210d51a302c7906e > Author: Lars Wendler <polynomial-c@gentoo.org> > AuthorDate: 2022-03-28 19:31:12 +0000 > Commit: Lars Wendler <polynomial-c@gentoo.org> > CommitDate: 2022-03-28 19:31:34 +0000 > > net-fs/samba: Added dev-perl/JSON to DEPEND > > Bug: https://bugs.gentoo.org/836167 > Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> > > net-fs/samba/samba-4.16.0.ebuild | 1 + > 1 file changed, 1 insertion(+) This did not fix it for me; I am still getting the same error. I already had dev-perl/JSON installed. Sorry for the noise, but it seems I spoke too soon. After emerging JSON the build of samba progressed past where it failed before and continued, so I shut off the monitor and went to bed. Upon waking this morning I find that it indeed failed again. [2736/3893] Linking bin/default/third_party/heimdal_build/libroken-samba4.inst.so [2737/3893] Linking bin/default/third_party/heimdal_build/libgss-preauth-samba4.inst.so [2738/3893] Compiling third_party/heimdal/kdc/mssfu.c [2739/3893] Compiling third_party/heimdal/kdc/krb5tgs.c [2740/3893] Compiling third_party/heimdal/kdc/fast.c [2741/3893] Compiling third_party/heimdal/kdc/kdc-plugin.c In file included from ../../third_party/heimdal/kdc/kdc_locl.h:46, from ../../third_party/heimdal/kdc/mssfu.c:34: third_party/heimdal/kdc/kdc-private.h:224:9: error: unknown type name ‘gss_OID_set’ 224 | gss_OID_set */*oidsp*/); | ^~~~~~~~~~~ In file included from ../../third_party/heimdal/kdc/mssfu.c:34: ../../third_party/heimdal/kdc/kdc_locl.h:116:5: error: unknown type name ‘gss_OID_set’ 116 | gss_OID_set gss_mechanisms_allowed; | ^~~~~~~~~~~ ../../third_party/heimdal/kdc/kdc_locl.h:117:5: error: unknown type name ‘gss_OID_set’ 117 | gss_OID_set gss_cross_realm_mechanisms_allowed; | ^~~~~~~~~~~ In file included from ../../third_party/heimdal/kdc/kdc_locl.h:46, from ../../third_party/heimdal/kdc/krb5tgs.c:34: third_party/heimdal/kdc/kdc-private.h:224:9: error: unknown type name ‘gss_OID_set’ 224 | gss_OID_set */*oidsp*/); | ^~~~~~~~~~~ In file included from ../../third_party/heimdal/kdc/krb5tgs.c:34: ../../third_party/heimdal/kdc/kdc_locl.h:116:5: error: unknown type name ‘gss_OID_set’ 116 | gss_OID_set gss_mechanisms_allowed; | ^~~~~~~~~~~ ../../third_party/heimdal/kdc/kdc_locl.h:117:5: error: unknown type name ‘gss_OID_set’ 117 | gss_OID_set gss_cross_realm_mechanisms_allowed; | ^~~~~~~~~~~ In file included from ../../third_party/heimdal/kdc/kdc_locl.h:46, from ../../third_party/heimdal/kdc/fast.c:36: third_party/heimdal/kdc/kdc-private.h:224:9: error: unknown type name ‘gss_OID_set’ 224 | gss_OID_set */*oidsp*/); | ^~~~~~~~~~~ In file included from ../../third_party/heimdal/kdc/fast.c:36: ../../third_party/heimdal/kdc/kdc_locl.h:116:5: error: unknown type name ‘gss_OID_set’ 116 | gss_OID_set gss_mechanisms_allowed; | ^~~~~~~~~~~ ../../third_party/heimdal/kdc/kdc_locl.h:117:5: error: unknown type name ‘gss_OID_set’ 117 | gss_OID_set gss_cross_realm_mechanisms_allowed; | ^~~~~~~~~~~ In file included from ../../third_party/heimdal/kdc/kdc_locl.h:46, from ../../third_party/heimdal/kdc/kdc-plugin.c:36: third_party/heimdal/kdc/kdc-private.h:224:9: error: unknown type name ‘gss_OID_set’ 224 | gss_OID_set */*oidsp*/); | ^~~~~~~~~~~ In file included from ../../third_party/heimdal/kdc/kdc-plugin.c:36: ../../third_party/heimdal/kdc/kdc_locl.h:116:5: error: unknown type name ‘gss_OID_set’ 116 | gss_OID_set gss_mechanisms_allowed; | ^~~~~~~~~~~ ../../third_party/heimdal/kdc/kdc_locl.h:117:5: error: unknown type name ‘gss_OID_set’ 117 | gss_OID_set gss_cross_realm_mechanisms_allowed; | ^~~~~~~~~~~ Waf: Leaving directory `/var/tmp/portage/net-fs/samba-4.16.0/work/samba-4.16.0-abi_x86_32.x86/bin/default' Build failed -> task in 'kdc.objlist' failed with exit status 1 (run with -v to display more information) -> task in 'kdc.objlist' failed with exit status 1 (run with -v to display more information) -> task in 'kdc.objlist' failed with exit status 1 (run with -v to display more information) -> task in 'kdc.objlist' failed with exit status 1 (run with -v to display more information) * ERROR: net-fs/samba-4.16.0::gentoo failed (install phase): * Make install failed * * Call stack: * ebuild.sh, line 127: Called src_install * environment, line 4239: Called multilib-minimal_src_install * environment, line 2929: Called multilib_foreach_abi 'multilib-minimal_abi_src_install' * environment, line 3159: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_install' * environment, line 2841: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_install' * environment, line 2839: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_install' * environment, line 799: Called multilib-minimal_abi_src_install * environment, line 2919: Called multilib_src_install * environment, line 3389: Called waf-utils_src_install * environment, line 5404: Called die * The specific snippet of code: * "${WAF_BINARY}" --destdir="${D}" "${@}" install || die "Make install failed"; * * If you need support, post the output of `emerge --info '=net-fs/samba-4.16.0::gentoo'`, * the complete build log and the output of `emerge -pqv '=net-fs/samba-4.16.0::gentoo'`. * The complete build log is located at '/var/log/portage/net-fs:samba-4.16.0:20220329-040104.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/net-fs/samba-4.16.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-fs/samba-4.16.0/temp/environment'. * Working directory: '/var/tmp/portage/net-fs/samba-4.16.0/work/samba-4.16.0-abi_x86_32.x86' * S: '/var/tmp/portage/net-fs/samba-4.16.0/work/samba-4.16.0' [U] net-fs/samba Available versions: [m](~)4.13.4^t[1] 4.14.12-r2^t 4.15.4-r2^t (~)4.15.5-r2^t (~)4.15.6^t (~)4.16.0^t {acl addc addns ads ceph client cluster cups debug dmapi fam glusterfs gpg iprint json ldap ntvfs pam profiling-data python quota +regedit selinux snapper spotlight syslog system-heimdal +system-mitkrb5 systemd test winbind zeroconf ABI_MIPS="n32 n64 o32" ABI_S390="32 64" ABI_X86="32 64 x32" CPU_FLAGS_X86="aes" KERNEL="linux" PYTHON_SINGLE_TARGET="python3_7 python3_8 python3_9 python3_10"} Installed versions: 4.15.5-r2^t(06:12:02 AM 03/26/2022)(acl client pam regedit winbind -addc -ads -ceph -cluster -cups -debug -fam -glusterfs -gpg -iprint -json -ldap -profiling-data -python -quota -selinux -snapper -spotlight -syslog -system-heimdal -system-mitkrb5 -systemd -test -zeroconf ABI_MIPS="-n32 -n64 -o32" ABI_S390="-32 -64" ABI_X86="32 64 -x32" CPU_FLAGS_X86="-aes" PYTHON_SINGLE_TARGET="python3_9 -python3_8 -python3_10") I see the same - the JSON perl package addition now gets it to failing with ../../third_party/heimdal/kdc/kdc_locl.h:116:5: error: unknown type name ‘gss_OID_set’ Didn't try changing to system-mitkrb5 , but seems like that'd get over this issue (although not desired, since it's easier to just use the heimdal bundled with Samba...). I have similar issues here (apart from the JSON issue): [1731/4180] Compiling source4/lib/socket/connect_multi.c 19:59:00 runner ['armv7a-unknown-linux-gnueabihf-gcc', '-D_SAMBA_BUILD_=4', '-DHAVE_CONFIG_H=1', '-O2', '-pipe', '-march=armv7-a', '-mfpu=vfpv3-d16', '-mfloat-abi=hard', '-MMD', '-D_GNU_SOURCE=1', '-D_XOPEN_SOURCE_EXTENDED=1', '-DHAVE_CONFIG_H=1', '-fPIC', '-D__STDC_WANT_LIB_EXT1__=1', '-D_LARGEFILE_SOURCE', '-D_FILE_OFFSET_BITS=64', '-D_REENTRANT', '-fstack-protector-strong', '-fstack-clash-protection', '-DSTATIC_samba_socket_MODULES=NULL', '-DSTATIC_samba_socket_MODULES_PROTO=extern void __samba_socket_dummy_module_proto(void)', '-Isource4/lib/socket', '-I../../source4/lib/socket', '-Iinclude/public', '-I../../include/public', '-Isource4', '-I../../source4', '-Ilib', '-I../../lib', '-Isource4/lib', '-I../../source4/lib', '-Isource4/include', '-I../../source4/include', '-Iinclude', '-I../../include', '-Ilib/replace', '-I../../lib/replace', '-I.', '-I../..', '-Ilibcli/util', '-I../../libcli/util', '-Isource4/libcli', '-I../../source4/libcli', '-Ilibrpc', '-I../../librpc', '-Ilib/socket', '-I../../lib/socket', '-Ilib/tsocket', '-I../../lib/tsocket', '-Ilib/util/var/tmp/portage/net-fs/samba-4.16.0/work/samba-4.16.0-.arm/third_party/gpfs', '-I../../lib/util/var/tmp/portage/net-fs/samba-4.16.0/work/samba-4.16.0-.arm/third_party/gpfs', '-Ilibcli/security', '-I../../libcli/security', '-Ilib/util/charset', '-I../../lib/util/charset', '-Isource4/lib/events', '-I../../source4/lib/events', '-Ilibcli/nbt', '-I../../libcli/nbt', '-Ithird_party/heimdal/lib/roken', '-I../../third_party/heimdal/lib/roken', '-Ithird_party/heimdal/include', '-I../../third_party/heimdal/include', '-Ithird_party/heimdal_build/include', '-I../../third_party/heimdal_build/include', '-Ithird_party/heimdal_build', '-I../../third_party/heimdal_build', '-Idynconfig', '-I../../dynconfig', '-Ilib/crypto', '-I../../lib/crypto', '../../source4/lib/socket/connect_multi.c', '-c', '-o/var/tmp/portage/net-fs/samba-4.16.0/work/samba-4.16.0-.arm/bin/default/source4/lib/socket/connect_multi.c.7.o', '-I/usr/include/et'] In file included from ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:40, from ../../lib/replace/system/gssapi.h:43, from ../../lib/krb5_wrap/gss_samba.h:27, from ../../lib/krb5_wrap/gss_samba.c:23: ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_oid.h:9:8: error: unknown type name ‘GSSAPI_LIB_VARIABLE’ 9 | extern GSSAPI_LIB_VARIABLE gss_OID_desc __gss_krb5_copy_ccache_x_oid_desc; | ^~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_oid.h:9:41: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__gss_krb5_copy_ccache_x_oid_desc’ 9 | extern GSSAPI_LIB_VARIABLE gss_OID_desc __gss_krb5_copy_ccache_x_oid_desc; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_oid.h:12:8: error: unknown type name ‘GSSAPI_LIB_VARIABLE’ 12 | extern GSSAPI_LIB_VARIABLE gss_OID_desc __gss_krb5_get_tkt_flags_x_oid_desc; | ^~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_oid.h:12:41: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__gss_krb5_get_tkt_flags_x_oid_desc’ 12 | extern GSSAPI_LIB_VARIABLE gss_OID_desc __gss_krb5_get_tkt_flags_x_oid_desc; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_oid.h:15:8: error: unknown type name ‘GSSAPI_LIB_VARIABLE’ 15 | extern GSSAPI_LIB_VARIABLE gss_OID_desc __gss_krb5_extract_authz_data_from_sec_context_x_oid_desc; | ^~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_oid.h:15:41: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__gss_krb5_extract_authz_data_from_sec_context_x_oid_desc’ 15 | extern GSSAPI_LIB_VARIABLE gss_OID_desc __gss_krb5_extract_authz_data_from_sec_context_x_oid_desc; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_oid.h:18:8: error: unknown type name ‘GSSAPI_LIB_VARIABLE’ 18 | extern GSSAPI_LIB_VARIABLE gss_OID_desc __gss_krb5_compat_des3_mic_x_oid_desc; | ^~~~~~~~~~~~~~~~~~~ ......... In file included from ../../lib/replace/system/gssapi.h:43, from ../../lib/krb5_wrap/gss_samba.h:27, from ../../lib/krb5_wrap/gss_samba.c:23: ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:42:17: error: expected ‘;’ before ‘extern’ 42 | GSSAPI_CPP_START | ^ | ; ...... 57 | extern gss_OID_desc GSSAPI_LIB_VARIABLE __gss_krb5_nt_principal_name_oid_desc; | ~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:57:8: error: unknown type name ‘gss_OID_desc’ 57 | extern gss_OID_desc GSSAPI_LIB_VARIABLE __gss_krb5_nt_principal_name_oid_desc; | ^~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:57:41: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__gss_krb5_nt_principal_name_oid_desc’ 57 | extern gss_OID_desc GSSAPI_LIB_VARIABLE __gss_krb5_nt_principal_name_oid_desc; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:77:1: error: unknown type name ‘GSSAPI_LIB_FUNCTION’ 77 | GSSAPI_LIB_FUNCTION OM_uint32 GSSAPI_LIB_CALL | ^~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:77:31: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘GSSAPI_LIB_CALL’ 77 | GSSAPI_LIB_FUNCTION OM_uint32 GSSAPI_LIB_CALL | ^~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:77:31: error: unknown type name ‘GSSAPI_LIB_CALL’ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:82:1: error: unknown type name ‘GSSAPI_LIB_FUNCTION’ 82 | GSSAPI_LIB_FUNCTION OM_uint32 GSSAPI_LIB_CALL gsskrb5_register_acceptor_identity | ^~~~~~~~~~~~~~~~~~~ ............. ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:157:31: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘GSSAPI_LIB_CALL’ 157 | GSSAPI_LIB_FUNCTION OM_uint32 GSSAPI_LIB_CALL | ^~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:157:31: error: unknown type name ‘GSSAPI_LIB_CALL’ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:167:9: error: unknown type name ‘OM_uint32’ 167 | OM_uint32 type; | ^~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:168:9: error: unknown type name ‘OM_uint32’ 168 | OM_uint32 length; | ^~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:173:9: error: unknown type name ‘OM_uint32’ 173 | OM_uint32 sign_alg; | ^~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:174:9: error: unknown type name ‘OM_uint32’ 174 | OM_uint32 seal_alg; | ^~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:179:9: error: unknown type name ‘OM_uint32’ 179 | OM_uint32 have_acceptor_subkey; | ^~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:185:9: error: unknown type name ‘OM_uint32’ 185 | OM_uint32 version; | ^~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:186:9: error: unknown type name ‘OM_uint32’ 186 | OM_uint32 initiate; | ^~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:187:9: error: unknown type name ‘OM_uint32’ 187 | OM_uint32 endtime; | ^~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:188:9: error: unknown type name ‘OM_uint64’ 188 | OM_uint64 send_seq; | ^~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:189:9: error: unknown type name ‘OM_uint64’ 189 | OM_uint64 recv_seq; | ^~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:190:9: error: unknown type name ‘OM_uint32’ 190 | OM_uint32 protocol; | ^~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:196:9: error: unknown type name ‘OM_uint32’ 196 | OM_uint32 version; /* Structure version number */ | ^~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_krb5.h:203:1: error: unknown type name ‘GSSAPI_LIB_FUNCTION’ 203 | GSSAPI_LIB_FUNCTION OM_uint32 GSSAPI_LIB_CALL | ^~~~~~~~~~~~~~~~~~~ .......... In file included from ../../lib/replace/system/gssapi.h:47, from ../../lib/krb5_wrap/gss_samba.h:27, from ../../lib/krb5_wrap/gss_samba.c:23: ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:41:17: error: expected ‘;’ before ‘extern’ 41 | GSSAPI_CPP_START | ^ | ; ...... 49 | extern GSSAPI_LIB_VARIABLE gss_OID_desc __gss_spnego_mechanism_oid_desc; | ~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:49:8: error: unknown type name ‘GSSAPI_LIB_VARIABLE’ 49 | extern GSSAPI_LIB_VARIABLE gss_OID_desc __gss_spnego_mechanism_oid_desc; | ^~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:49:41: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__gss_spnego_mechanism_oid_desc’ 49 | extern GSSAPI_LIB_VARIABLE gss_OID_desc __gss_spnego_mechanism_oid_desc; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:56:1: error: unknown type name ‘GSSAPI_LIB_FUNCTION’ 56 | GSSAPI_LIB_FUNCTION OM_uint32 GSSAPI_LIB_CALL | ^~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:56:31: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘GSSAPI_LIB_CALL’ 56 | GSSAPI_LIB_FUNCTION OM_uint32 GSSAPI_LIB_CALL | ^~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:56:31: error: unknown type name ‘GSSAPI_LIB_CALL’ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:63:1: error: unknown type name ‘GSSAPI_LIB_FUNCTION’ 63 | GSSAPI_LIB_FUNCTION OM_uint32 GSSAPI_LIB_CALL | ^~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:63:31: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘GSSAPI_LIB_CALL’ 63 | GSSAPI_LIB_FUNCTION OM_uint32 GSSAPI_LIB_CALL | ^~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:63:31: error: unknown type name ‘GSSAPI_LIB_CALL’ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:74:1: error: unknown type name ‘GSSAPI_LIB_FUNCTION’ 74 | GSSAPI_LIB_FUNCTION OM_uint32 GSSAPI_LIB_CALL | ^~~~~~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:74:31: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘GSSAPI_LIB_CALL’ 74 | GSSAPI_LIB_FUNCTION OM_uint32 GSSAPI_LIB_CALL | ^~~~~~~~~~~~~~~ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:74:31: error: unknown type name ‘GSSAPI_LIB_CALL’ ../../third_party/heimdal/lib/gssapi/gssapi/gssapi_spnego.h:85:15: error: expected ‘;’ before ‘struct’ 85 | GSSAPI_CPP_END | ^ | ; In file included from ../../lib/krb5_wrap/gss_samba.c:23: ../../lib/krb5_wrap/gss_samba.h:44:35: error: unknown type name ‘OM_uint32’ 44 | uint32_t smb_gss_krb5_import_cred(OM_uint32 *minor_status, krb5_context ctx, | ^~~~~~~~~ ../../lib/krb5_wrap/gss_samba.h:46:55: error: unknown type name ‘gss_cred_id_t’ 46 | krb5_keytab keytab, gss_cred_id_t *cred); | ^~~~~~~~~~~~~ ../../lib/krb5_wrap/gss_samba.c:60:55: error: unknown type name ‘gss_cred_id_t’ 60 | krb5_keytab keytab, gss_cred_id_t *cred) | ^~~~~~~~~~~~~ Waf: Leaving directory `/var/tmp/portage/net-fs/samba-4.16.0/work/samba-4.16.0-.arm/bin/default' Build failed -> task in 'krb5samba.objlist' failed with exit status 1: {task 3021652120: c gss_samba.c -> gss_samba.c.1.o} I try to compile on a Raspi 4. I saw different errors using distcc. I can supply complete log files for both cases, if this would be helpful. I run a AD-DC on the raspi, and hence these were my use flags: net-fs/samba addc ads winbind smbclient ldb netapi -system-mitkrb5 -system-heimdal syslog addns ldap gnutls json I admit, that I added json, because it complained at some point in time on that keyword missing. Apart from that, I don't seen any apparent use in json for my purposes. If I run waf with PYTHONHASHSEED=1 (which is what upstream's Makefile does) it builds for me. That is: --- /usr/portage/net-fs/samba/samba-4.16.0.ebuild 2022-03-28 19:40:06.000000000 +0000 +++ /usr/local/portage/private/net-fs/samba/samba-4.16.0.ebuild 2022-04-01 14:37:38.123608718 +0000 @@ -250,16 +250,16 @@ myconf+=( --with-shared-modules=DEFAULT,!vfs_snapper ) fi - CPPFLAGS="-I${SYSROOT}${EPREFIX}/usr/include/et ${CPPFLAGS}" \ + PYTHONHASHSEED=1 CPPFLAGS="-I${SYSROOT}${EPREFIX}/usr/include/et ${CPPFLAGS}" \ waf-utils_src_configure ${myconf[@]} } multilib_src_compile() { - waf-utils_src_compile + PYTHONHASHSEED=1 waf-utils_src_compile } multilib_src_install() { - waf-utils_src_install + PYTHONHASHSEED=1 waf-utils_src_install # Make all .so files executable find "${ED}" -type f -name "*.so" -exec chmod +x {} + || die Upstream made that change to avoid some spurious rebuilds (see https://github.com/samba-team/samba/commit/19a4d3ca692e864a2ae6c8c496e7eb08cded612f), but I think it may have become more load-bearing than they probably intended: I've had both emerge (with the "unknown type name ‘gss_OID_set’" error) and manual builds (with that error as well as the "unknown type name ‘GSSAPI_LIB_VARIABLE’" error) repeatedly fail, and stop failing if I start over with PYTHONHASHSEED=1. I'm not sure *why* this helps (my hunch is that it has to do with the order of -I flags passed to the compiler, given there's more than one of a few headers like gssapi.h and it looks like the wrong thing may happen if it includes the wrong one, but there's enough #ifdef involved I haven't fully tracked it down). (In reply to Marien Zwart from comment #10) >[...] > I'm not sure *why* this helps (my hunch is that it has to do with the order > of -I flags passed to the compiler, given there's more than one of a few > headers like gssapi.h and it looks like the wrong thing may happen if it > includes the wrong one, but there's enough #ifdef involved I haven't fully > tracked it down). Yeah, it's a bit like using parallel builds when upstream don't test it Should it work? Yes. Does that mean it will? No. :) Nice debugging work. We should add the option I think. This worked for me: sudo bash -c 'export PYTHONHASHSEED=1; emerge -v1 net-fs/samba' (In reply to Erik Zeek from comment #12) > This worked for me: > > sudo bash -c 'export PYTHONHASHSEED=1; emerge -v1 net-fs/samba' This worked for me, too. I have now put the variable in `package.env` fixing the build for this version of the package on my machine, i.e. echo 'PYTHONHASHSEED=1' >> /etc/portage/env/pythonhashseed.conf echo '=net-fs/samba-4.16.0 pythonhashseed.conf' >> /etc/portage/package.env Hope that helps as a temporary workaround. (In reply to Patrick Holthaus from comment #13) > (In reply to Erik Zeek from comment #12) > > This worked for me: > > > > sudo bash -c 'export PYTHONHASHSEED=1; emerge -v1 net-fs/samba' > > This worked for me, too. I have now put the variable in `package.env` fixing > the build for this version of the package on my machine, i.e. > > echo 'PYTHONHASHSEED=1' >> /etc/portage/env/pythonhashseed.conf > echo '=net-fs/samba-4.16.0 pythonhashseed.conf' >> /etc/portage/package.env > > Hope that helps as a temporary workaround. It does indeed, thank you! Hit this bug when rebuilding samba as a result of the dev-libs/icu bump to 71.1; something must have changed in the last two weeks or so... The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d092dfd7485f030626d55087e004e3996f0986e4 commit d092dfd7485f030626d55087e004e3996f0986e4 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-04-12 06:57:18 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-04-12 06:57:18 +0000 net-fs/samba: fix race condition during build It's a bit gross but no different from having to force -j1 if upstream clearly aren't testing w/ it. Upstream force PYTHONHASHSEED=1 (which gives determinism) in their builds, so we need to as well, to avoid confusing failures. Closes: https://bugs.gentoo.org/836167 Acked-by: David Seifert <soap@gentoo.org> Thanks-to: Marien Zwart <marien.zwart@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> net-fs/samba/samba-4.15.6.ebuild | 6 +++--- net-fs/samba/samba-4.16.0.ebuild | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) |