if [ g77 is not on the system, aka - `USE='-f77' emerge gcc` ]; then lapack inappropriately merges (see below for details); `emerge app-misc/grass` will find the lapack dependency && not the lapack library; fi Could this be symptomatic of a bug in portage too... failing to catch the Error 127? breakMe # emerge lapack Calculating dependencies ...done! >>> emerge (1 of 1) app-sci/lapack-3.0 to / >>> md5 src_uri ;-) lapack.tgz >>> Unpacking source... >>> Unpacking lapack.tgz to /var/tmp/portage/lapack-3.0/work >>> Source unpacked. g77 -pipe -O3 -march=pentium2 -fomit-frame-pointer -frename-registers -fmove-all -movables -fpic -momit-leaf-frame-pointer -fno-crossjumping -maccumulate-outgoin g-args -c -o cbdsqr.o cbdsqr.f make: g77: Command not found make: *** [cbdsqr.o] Error 127 >>> Install lapack-3.0 into /var/tmp/portage/lapack-3.0/image/ category app-sci /usr/lib/portage/bin/dolib.a: SRC/liblapack.a does not exist man: prepallstrip: strip: >>> Completed installing into /var/tmp/portage/lapack-3.0/image/ >>> Merging app-sci/lapack-3.0 to / sfperms --- /usr/ --- /usr/lib/ >>> Safely unmerging already-installed instance... --- !empty dir /usr/lib --- !empty dir /usr >>> original instance of package unmerged safely. * Caching service dependencies... >>> app-sci/lapack-3.0 merged. breakMe # Reproducible: Always Steps to Reproduce: 1. `USE='-f77' emerge gcc 2. emerge lapack 3. emerge grass Actual Results: See details Expected Results: lapack should not have merged while app-misc/grass ebuild appears to be good.
Another one hanging on f77. *** This bug has been marked as a duplicate of 57396 ***
