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