When gcc is built with USE="-fortran" dev-libs/papi-5.3.0 fails to compile. Excerpt from the build.log (attached): ar rv libtestlib.a do_loops.o test_utils.o dummy.o clockcore.o ftests_util.o ar: creating libtestlib.a a - do_loops.o a - test_utils.o a - dummy.o a - clockcore.o ar: ftests_util.o: No such file or directory Makefile:14: recipe for target 'all' failed make[1]: *** [all] Error 1 make[1]: Leaving directory '/var/tmp/portage/dev-libs/papi-5.3.0/work/papi-5.3.0/src/testlib' Makefile.inc:234: recipe for target 'testlib' failed make: *** [testlib] Error 2 make: *** Waiting for unfinished jobs.... Reproducible: Always Steps to Reproduce: 1. USE="-fortran" emerge -1vO gcc 2. emerge -v =dev-libs/papi-5.3.0 Actual Results: dev-libs/papi-5.3.0 fails to compile. Expected Results: dev-libs/papi-5.3.0 should complain about missing fortran support in gcc. The issue is easily fixed by recompiling gcc with fortran support. Apart from that papi 5.4.0 was released not that long ago: http://icl.cs.utk.edu/papi/news/news.html?id=348
Created attachment 390506 [details] papi-5.3.0_build.log
Missing fortran support being the culprit is mentioned here: http://comments.gmane.org/gmane.comp.linux.papi/1276
nof77 -I. -I.. -O2 -pipe -Dlinux -Wall -ffixed-line-length-132 -c ftests_util.F I don't see how that command doesn't fail. But it doesn't.
Created attachment 390508 [details] emerge --info of the system
Can you please try again after emerge --sync?
Looks good, thanks :) # emerge -pv papi The following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details) # required by virtual/fortran-0 # required by dev-libs/papi-5.3.0 # required by papi (argument) >=sys-devel/gcc-4.8.3:4.8 fortran
