x86_64-gentoo-linux-musl-gcc -DHAVE_CONFIG_H -I. -O2 -pipe -march=native -fno-common -falign-functions=32:25:16 -c -o ascii_generator.o ascii_generator.c x86_64-gentoo-linux-musl-gcc -DHAVE_CONFIG_H -I. -O2 -pipe -march=native -fno-common -falign-functions=32:25:16 -c -o troff_generator.o troff_generator.c troff_generator.c:33:10: fatal error: sys/unistd.h: No such file or directory 33 | #include <sys/unistd.h> | ^~~~~~~~~~~~~~ compilation terminated. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-20200316-165821 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-gentoo-linux-musl-9.3.0 * clang version 10.0.0 Target: x86_64-gentoo-linux-musl Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.0 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.7 [3] python3.6 [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.41.1 * repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Wed, 18 Mar 2020 13:38:27 +0000 emerge -qpvO app-text/robodoc [ebuild N ] app-text/robodoc-4.99.43 USE="-examples"
Created attachment 623072 [details] emerge-info.txt
Created attachment 623074 [details] app-text:robodoc-4.99.43:20200320-023853.log
Created attachment 623076 [details] emerge-history.txt
Created attachment 623078 [details] environment
Created attachment 623080 [details] etc.portage.tbz2
Created attachment 623082 [details] logs.tbz2
Created attachment 623084 [details] temp.tbz2
Hy. This is due to musl and should be patched upstream. The placement of unistd.h differs as follows: with musl: /usr/include/unistd.h with gnu: /usr/include/unistd.h /usr/include/sys/unistd.h (includes previous) This is a rather quick fix upstream and this particular header gets included in troff_generator.c only. I'd rather build the source against musl completely to find any other errors related to libc and patch them all in one go (another one used which
Created attachment 623864 [details, diff] patch to build against musl the sources build fine against musl on a amd64-musl-hardened and robodoc works just fine
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f8448ce2f5cf828cdf63df45f52eb643cb9a937c commit f8448ce2f5cf828cdf63df45f52eb643cb9a937c Author: Ovidiu-Dan Bogat <4z0r@ovidiu.at> AuthorDate: 2020-03-21 15:07:51 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2020-03-25 13:45:24 +0000 app-text/robodoc: revision to build against musl Closes: https://bugs.gentoo.org/713616 Signed-off-by: Ovidiu-Dan Bogat <ovi@ovidiu.at> Package-Manager: Portage-2.3.89, Repoman-2.3.20 Closes: https://github.com/gentoo/gentoo/pull/15035 Signed-off-by: Joonas Niilola <juippis@gentoo.org> .../robodoc/files/robodoc-4.99.43_clean_libc.patch | 13 +++++++++ app-text/robodoc/robodoc-4.99.43-r1.ebuild | 32 ++++++++++++++++++++++ 2 files changed, 45 insertions(+)