Bug 323555 – fortran.eclass forbids FC=${CHOST}-gfortran

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Nathan Phillip Brink (binki) (RETIRED) 2010-06-11 12:41:48 UTC]

Reproducable on portage with
$ FC=$(portageq envvar CHOST)-gfortran emerge -v blas-atlas

Would also cause problems with the -gfortran that tc-getPROG() returns. ${CHOST}-gfortran is valid and must be supported by the eclass.

Perhaps the eclass can automatically strip ${CHOST} from FC or just ignore everything before and including the last `-' in FC.

[Comment 1 Nathan Phillip Brink (binki) (RETIRED) 2010-06-11 12:44:55 UTC]

Created attachment 234939 [details]
build.log

[Comment 2 Nathan Phillip Brink (binki) (RETIRED) 2010-06-11 12:46:18 UTC]

Created attachment 234941 [details]
die.env

[Comment 3 Nathan Phillip Brink (binki) (RETIRED) 2010-06-11 12:46:32 UTC]

Created attachment 234943 [details]
emerge --info

[Comment 4 Nathan Phillip Brink (binki) (RETIRED) 2010-07-16 01:35:03 UTC]

Created attachment 238971 [details, diff]
allows programs to compile if FC=$(portageq envvar CHOST)-gfortran

This patch causes the ebuilds not to die just because FC=$(portageq envvar CHOST)-gfortran.

Some packages, like xfoil, test ${FOTRANC} = "gfortran" instead of using fortran_patch(). I couldn't find a test-case for my modified fortran_patch() in the time I gave myself.

[Comment 5 Justin Lecher (RETIRED) 2011-04-01 11:01:11 UTC]

fortran.eclass not used anymore in the tree