1 |
On 08:46 Fri 17 Dec , justin wrote: |
2 |
> Hi all, |
3 |
> |
4 |
> my removal of the fortran.eclass has left many packages in a broken |
5 |
> state. Many packages and/or their buildsystem depend on |
6 |
> (x86_64|i686)-linux-gnu-gfortran being simple named gfortran. For |
7 |
> example the cns package uses the Makefile.gfortran, which was formerly |
8 |
> Makefile.${FORTRANC}, but now a Makefile.$(tc-getFC) doesn't work. Same |
9 |
> for Makefile.ifort vs Makefile.ifc. Similar happasn to many packages and |
10 |
> excuse me to have some problems today. Iwill fix that. |
11 |
> |
12 |
> So my proposal is to create a fortran-ng.eclass which gives us simply |
13 |
> the a variable similar to FORTRANC representing the old style naming, so |
14 |
> that not every ebuild has to implement it again. |
15 |
> |
16 |
> case $(tc-getFC) in |
17 |
> *gfortran* ) |
18 |
> FCOMP="gfortran" ;; |
19 |
> ifort ) |
20 |
> FCOMP="ifc" ;; |
21 |
> * ) |
22 |
> FCOMP=$(tc-getFC) ;; |
23 |
> esac |
24 |
|
25 |
I wonder if this would instead merit a small separate function in |
26 |
toolchain-funcs. |
27 |
|
28 |
-- |
29 |
Thanks, |
30 |
Donnie |
31 |
|
32 |
Donnie Berkholz |
33 |
Sr. Developer, Science Team |
34 |
Gentoo Linux |
35 |
Blog: http://dberkholz.wordpress.com |