https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-lang/nim-1.6.6-r1 calls cc directly. Discovered on: amd64 (internal ref: ci) NOTE: As per QA policy, toolchain tools must not be called directly because they can cause issue in cross-compiling and because is not possible use a different CC implementation (like clang). To reproduce, please use sys-devel/gcc-config[-native-symlinks], sys-devel/binutils-config[-native-symlinks].
CC'ing also the author of the commit (38ad8d4290f37de7d1de2aa96a8dedbc160b3123)
Created attachment 791372 [details] build.log build log and emerge --info
Error(s) that match a know pattern: /bin/sh: line 1: gcc: command not found Error: execution of an external compiler program 'gcc -c -w -fmax-errors=3 -I/var/tmp/portage/dev-lang/nim-1.6.6-r1/work/nim-1.6.6/lib -I/var/tmp/portage/dev-lang/nim-1.6.6-r1/work/nim-1.6.6/compiler -o /var/tmp/portage/dev-lang/nim-1.6.6-r1/work/nim-1.6.6/nimcache/d_linux_amd64/linenoise.c.o /var/tmp/portage/dev-lang/nim-1.6.6-r1/work/nim-1.6.6/lib/wrappers/linenoise/linenoise.c' failed with exit code: 127 FAILURE
This only happens in stage1. And I don't think it can be fixed.
(In reply to Anna Vyalkova from comment #4) > This only happens in stage1. And I don't think it can be fixed. Isn't the problem the --skipUserCfg? By making it a non-usercfg it doesn't ignore it anymore e.g. - cat > nim.cfg <<- EOF || die "Failed to create Nim config" + cat >> config/nim.cfg <<- EOF || die "Failed to create Nim config" It works with -native-symlinks and respected flags for me then. Albeit I know next to nothing about nim, so unsure if that really makes sense.
Should have been closed with https://github.com/gentoo/gentoo/pull/26399
