> Why? It should look for it first in 32/finclude, sure, but if not found,
> should fall back to finclude dir, where it is found.
> Does it differ between 32-bit and 64-bit compilation?
Module files are target- and ABI-dependent and can differ between multilibs.
Thus gfortran only looks for intr
On Tue, May 31, 2016 at 03:36:14PM +0200, FX wrote:
> Richard, Jakub, or any global write maintainer: can I get a review on this
> one-word patch?
>
> --
>
> The attached patch allows libgomp to install its Fortran modules in the
> correct multilib-aware directories, just like l
Richard, Jakub, or any global write maintainer: can I get a review on this
one-word patch?
--
The attached patch allows libgomp to install its Fortran modules in the correct
multilib-aware directories, just like libgfortran does.
Without it, multilib Fortran OpenMP code using th
ping
> Le 3 mai 2016 à 23:25, FX a écrit :
>
> The attached patch allows libgomp to install its Fortran modules in the
> correct multilib-aware directories, just like libgfortran does.
> Without it, multilib Fortran OpenMP code using the modules fails to compile
> because the modules are not
