Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On 21/06/11 08:59, justin wrote:
> Hello,
>
> We just included an eclass to simplify the fortran compiler dependency
> and testing in ebuilds.
>
> For the simplest case, which is most probably the way you want it,
> simply add "fortran-2" to you inherit line. The only phase function
> exported is pkg_setup, so take care to add "fortran-2_pkg_setup" in case
> you redefined pkg_setup.
>
> This will depend on a fortran compiler and check additionally for
> general compiler functionality.
>
> Two specialist cases are support.
>
> First, you need openmp support from the fortran compiler, then simply
> define "FORTRAN_NEED_OPENMP=1".
>
> Second, you need a different fortran dialect. Normally this can be
> identified, if the source files have different suffixes then .f e.g. .f90.
> Simply define FORTRAN_STANDARD with the dialects you need.
> Currently supported are the dialects from 77, 90, 95 and 03. 08 is
> currently not, due to the lack of a working compiler.
>
> I hope this will fix the problems due to missing fortran compilers.
>
> justin
>
UPDATE:
You need to add virtual/fortran to your dependencies. I just removed the
unconditional dependency from the eclass, in order to allow conditional
fortran support in the ebuilds.
|
|
