Re: [Pdl-devel] ExtUtils:F77 new version 1.18 for testing

2015-11-15 Thread sisyphus1
-Original Message- From: sisyph...@optusnet.com.au > Is it possible to just specify *all* of the possible libraries that might > be needed, skip the validation, and leave it to EU::MM to automatically > remove the ones that don't exist ? Didn't really give a very good account of this

Re: [Pdl-devel] ExtUtils:F77 new version 1.18 for testing

2015-11-15 Thread sisyphus1
-Original Message- From: Karl Glazebrook Sent: Monday, November 16, 2015 1:32 PM To: Chris Marshall Cc: pdl-devel ; sisyph...@optusnet.com.au Subject: Re: [Pdl-devel] ExtUtils:F77 new version 1.18 for testing > Hi Rob > > Can you help with this? Ideally a patch > > I was wondering how uni

Re: [Pdl-devel] ExtUtils:F77 new version 1.18 for testing

2015-11-15 Thread Karl Glazebrook
Hi Rob Can you help with this? Ideally a patch I was wondering how universal these gfortran libs were…. if we don’t include them then will get runtime errors on OS X etc. I was hoping it would be the same across all gfortran architectures. Does anyone know an automatic way to spit out a librar

Re: [Pdl-devel] ExtUtils:F77 new version 1.18 for testing

2015-11-15 Thread Chris Marshall
The only sure way to validate a compiler and library is to try to use it. Static checks for files and filenames are not robust because of the many possible paths, file names, file extensions,... Looking at the code changed, it looks like you've added OSX randomness to cygwin. Maybe some condition

Re: [Pdl-devel] ExtUtils:F77 new version 1.18 for testing

2015-11-15 Thread Chris Marshall
The repo magic looks good, Karl. Some of the extra checking breaks for cygwin. Which does have gfortran. I get this from make test: perl -Mblib t/require.t 1..2 ExtUtils::F77: Version 1.19 Loaded ExtUtils::F77 version 1.19 Found compiler gfortran ExtUtils::F77: gfortran version 4.9.3 ExtUtils: