1 |
Hello, |
2 |
|
3 |
We just included an eclass to simplify the fortran compiler dependency |
4 |
and testing in ebuilds. |
5 |
|
6 |
For the simplest case, which is most probably the way you want it, |
7 |
simply add "fortran-2" to you inherit line. The only phase function |
8 |
exported is pkg_setup, so take care to add "fortran-2_pkg_setup" in case |
9 |
you redefined pkg_setup. |
10 |
|
11 |
This will depend on a fortran compiler and check additionally for |
12 |
general compiler functionality. |
13 |
|
14 |
Two specialist cases are support. |
15 |
|
16 |
First, you need openmp support from the fortran compiler, then simply |
17 |
define "FORTRAN_NEED_OPENMP=1". |
18 |
|
19 |
Second, you need a different fortran dialect. Normally this can be |
20 |
identified, if the source files have different suffixes then .f e.g. .f90. |
21 |
Simply define FORTRAN_STANDARD with the dialects you need. |
22 |
Currently supported are the dialects from 77, 90, 95 and 03. 08 is |
23 |
currently not, due to the lack of a working compiler. |
24 |
|
25 |
I hope this will fix the problems due to missing fortran compilers. |
26 |
|
27 |
justin |