bzip2: /var/tmp/portage/dev-lang/ghc-9.0.2/distdir/ghc-bin-9.0.2-x86_64-pc-linux-gnu.tbz2: trailing garbage after EOF ignored >>> Source unpacked in /var/tmp/portage/dev-lang/ghc-9.0.2/work >>> Preparing source in /var/tmp/portage/dev-lang/ghc-9.0.2/work/ghc-9.0.2 ... ln: failed to create symbolic link '/var/tmp/portage/dev-lang/ghc-9.0.2/work/usr/lib/ghc-9.0.2/include/ffi.h': No such file or directory * ERROR: dev-lang/ghc-9.0.2::gentoo failed (prepare phase): * (no error message) ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl_hardened-j4-20220723-104412 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-gentoo-linux-musl-12.1.1 * clang/llvm (if any): Python 3.10.5 Available Rust versions: [1] rust-1.62.1 * php cli: HEAD of ::gentoo commit b542ef4a4d5e343617115f29b72a3b73ed29a0ef Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Jul 23 13:01:41 2022 +0000 2022-07-23 13:01:41 UTC emerge -qpvO dev-lang/ghc [ebuild N ] dev-lang/ghc-9.0.2 USE="doc gmp (-big-endian) -binary -elfutils -ghcbootstrap -ghcmakebinary -numa -profile -test"
Created attachment 793493 [details] emerge-info.txt
Created attachment 793496 [details] dev-lang:ghc-9.0.2:20220723-143900.log
Created attachment 793499 [details] emerge-history.txt
Created attachment 793502 [details] environment
Created attachment 793505 [details] etc.portage.tar.bz2
Created attachment 793508 [details] temp.tar.bz2
This is not caused by musl. I'm hitting this too and my C library is glibc.
(In reply to Andrius Štikonas from comment #7) > This is not caused by musl. I'm hitting this too and my C library is glibc. ... with what profile?
(In reply to Sam James from comment #8) > (In reply to Andrius Štikonas from comment #7) > > This is not caused by musl. I'm hitting this too and my C library is glibc. > > ... with what profile? default/linux/amd64/17.1/desktop/plasma/systemd Sorry, somehow forgot to subscribe to this bug and missed the question.
Looks like this is triggered by USE="ghcbootstrap"
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f1a9b0bc9d6758d6dd960610a65019022deb04aa commit f1a9b0bc9d6758d6dd960610a65019022deb04aa Author: Jaak Ristioja <jaak@ristioja.ee> AuthorDate: 2022-07-28 22:02:58 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-07-30 09:20:26 +0000 dev-lang/ghc: Fixed symlink creation to non-existent directory [sam: USE=ghcbootstrap as noted by stikonas] Closes: https://bugs.gentoo.org/860276 Signed-off-by: Jaak Ristioja <jaak@ristioja.ee> Closes: https://github.com/gentoo/gentoo/pull/26640 Signed-off-by: Sam James <sam@gentoo.org> dev-lang/ghc/ghc-9.0.2.ebuild | 1 + 1 file changed, 1 insertion(+)
