it turns out gfortan is innocent. metview uses the magics++ package,
which caches the gfortran libraries in a cmake file fragment used by
metview.
I'm also the magics++ maintainer, and working on a solution now
regards
Alastair
On 25/05/2016 15:15, Alastair McKinstry wrote:
>
> metview doesn't s
metview doesn't seem to use a hard-coded version of gfortran but picks
up on the error somewhere in the bowels of its CMake code.
When built, the tools GeoTool binary uses the usual
/usr/lib/$ARCH/libgfortran.so.3 link. During building, it seems to pick
up the /usr/lib/gcc/* version as seen in th
2 matches
Mail list logo
