On 08:46 Fri 17 Dec , justin wrote:
> Hi all,
>
> my removal of the fortran.eclass has left many packages in a broken
> state. Many packages and/or their buildsystem depend on
> (x86_64|i686)-linux-gnu-gfortran being simple named gfortran. For
> example the cns package uses the Makefile.gfortran, which was formerly
> Makefile.${FORTRANC}, but now a Makefile.$(tc-getFC) doesn't work. Same
> for Makefile.ifort vs Makefile.ifc. Similar happasn to many packages and
> excuse me to have some problems today. Iwill fix that.
>
> So my proposal is to create a fortran-ng.eclass which gives us simply
> the a variable similar to FORTRANC representing the old style naming, so
> that not every ebuild has to implement it again.
>
> case $(tc-getFC) in
> *gfortran* )
> FCOMP="gfortran" ;;
> ifort )
> FCOMP="ifc" ;;
> * )
> FCOMP=$(tc-getFC) ;;
> esacI wonder if this would instead merit a small separate function in toolchain-funcs. -- Thanks, Donnie Donnie Berkholz Sr. Developer, Science Team Gentoo Linux Blog: http://dberkholz.wordpress.com
pgpvtUthPPw9l.pgp
Description: PGP signature
