make[1]: Leaving directory '/var/tmp/portage/net-fs/autofs-5.1.8/work/autofs-5.1.8/samples' x86_64-gentoo-linux-musl-gcc -pipe -march=native -fno-diagnostics-color -O2 -D_REENTRANT -D_FILE_OFFSET_BITS=64 -I/usr/include/tirpc -D_REENTRANT -D_FILE_OFFSET_BITS=64 -I/usr/include/tirpc -I../include -fPIC -D_GNU_SOURCE -DAUTOFS_MAP_DIR=\"/etc/autofs\" -DAUTOFS_CONF_DIR=\"/etc/conf.d\" -c mounts.c In file included from ../include/automount.h:26, from cat_path.c:18: ../include/hash.h:74:8: error: unknown type name '__always_inline' 74 | static __always_inline uint32_t hash_64(uint64_t val, unsigned int bits) | ^~~~~~~~~~~~~~~ ../include/hash.h:74:33: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'hash_64' 74 | static __always_inline uint32_t hash_64(uint64_t val, unsigned int bits) ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl_hardened-j4-20211210-222208 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-gentoo-linux-musl-11.2.1 * clang version 13.0.0 Target: x86_64-gentoo-linux-musl Thread model: posix InstalledDir: /usr/lib/llvm/13/bin /usr/lib/llvm/13 13.0.0 Python 3.9.9 Available Ruby profiles: (none found) Available Rust versions: [1] rust-bin-1.57.0 * php cli: HEAD of ::gentoo commit 5b3c1757053ea423912ad3d3ff637fe9470f13f1 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Dec 11 09:51:41 2021 +0000 2021-12-11 09:51:40 UTC emerge -qpvO net-fs/autofs [ebuild N ] net-fs/autofs-5.1.8 USE="(libtirpc) sasl -dmalloc -ldap -mount-locking (-systemd)"
Created attachment 758502 [details] emerge-info.txt
Created attachment 758503 [details] emerge-history.txt
Created attachment 758504 [details] environment
Created attachment 758505 [details] etc.portage.tar.bz2
Created attachment 758506 [details] logs.tar.bz2
Created attachment 758507 [details] net-fs:autofs-5.1.8:20211211-120206.log
Created attachment 758508 [details] temp.tar.bz2
hi @musl team The musl patch for 5.1.8 is forward ported from 5.1.6, and obviously it's broken now. I don't maintain or have a musl system myself, so unable to do further test. and more important I don't want to maintain the musl patch _downstream_. Instead, the best approach would be: pushing the patches to autofs upstream. I'd plan to drop the musl support for autofs during next bump, unless someone willing to step up to maintain it (or my suggestion would keeping the musl patches at @musl overlay)..
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=47fd280f578a9a3cc0259ce477e62153e2f67ca0 commit 47fd280f578a9a3cc0259ce477e62153e2f67ca0 Author: Sam James <sam@gentoo.org> AuthorDate: 2021-12-23 04:12:21 +0000 Commit: Yixun Lan <dlan@gentoo.org> CommitDate: 2021-12-23 07:05:13 +0000 net-fs/autofs: rebase musl patches, fix musl build for 5.1.8 These patches are also ready to be upstreamed once runtime tested. Closes: https://bugs.gentoo.org/828918 Closes: https://github.com/gentoo/gentoo/pull/23478 Signed-off-by: Sam James <sam@gentoo.org> Signed-off-by: Yixun Lan <dlan@gentoo.org> net-fs/autofs/Manifest | 1 + net-fs/autofs/autofs-5.1.8-r1.ebuild | 8 +++----- 2 files changed, 4 insertions(+), 5 deletions(-)
