* Using Module::Build * perl Build.PL --installdirs=vendor --libdoc= --destdir=/var/tmp/portage/media-gfx/graphite2-1.3.14/image --create_packlist=1 WARNING: the following files are missing in your kit: README Please inform the author. Can't exec "-shared": No such file or directory at /usr/lib64/perl5/5.32/ExtUtils/CBuilder/Base.pm line 342. Warning: ExtUtils::CBuilder not installed or no compiler detected Proceeding with configuration, but compilation may fail during Build Created MYMETA.yml and MYMETA.json Creating new 'Build' script for 'Text-Gr2' version '0.01' Building Text-Gr2 Error: no compiler detected to compile 'lib/Text/Gr2.c'. Aborting * ERROR: media-gfx/graphite2-1.3.14::gentoo failed (compile phase): * Compilation failed * * Call stack: * ebuild.sh, line 125: Called src_compile * environment, line 5100: Called perl-module_src_compile * environment, line 4083: Called die * The specific snippet of code: * ./Build build || die "Compilation failed";
Created attachment 692283 [details] graphite2-1.3.14:20210318-190242.log buildlog
Can't reproduce.
Please detail what environment you're using and include emerge --info in future, even if the error is 'obvious' because it saves a huge amount of time if it _isn't_.
Created attachment 692346 [details] graphite2.info emerge --info
LD=gcc "solved" the issue
I can reproduce now, but I don't think LD="" is something that should be taken into account. It's not uncommon that packages use LD=gcc by default too, overriding that globally is likely to give all sort of option errors regardless of linker. -fuse-ld=lld and/or a symlink would let you use lld anyway with less unnecessary errors (personally I prefer not to use lld with gcc though, and don't feel it's worth fixing issues at the moment).
It's the same issue as https://bugs.gentoo.org/641054
