From: justin <jlec@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Gentoo Science next meeting agenda - 5) fortran
Date: Fri, 17 Dec 2010 08:46:03 +0100 [thread overview]
Message-ID: <4D0B153B.6080603@gentoo.org> (raw)
In-Reply-To: <201012091628.34263.george@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
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) ;;
esac
justin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2010-12-17 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 12:55 [gentoo-science] Gentoo Science next meeting agenda - 5) fortran Kacper Kowalik
2010-12-09 15:28 ` George Shapovalov
2010-12-17 7:46 ` justin [this message]
2010-12-17 15:28 ` Donnie Berkholz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D0B153B.6080603@gentoo.org \
--to=jlec@gentoo.org \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox