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 conditional code is missing? There is no file *gcc_ext* on my system.
Cheers, Chris On 11/15/2015 09:54, Chris Marshall wrote: > 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::F77: gfortran version 4.9.3 > ExtUtils::F77: Using system=Cygwin compiler=GNU > Runtime: -L/usr/lib/gcc/x86_64-pc-cygwin/4.9.3 -lgcc_ext.10.5 > -lgcc_s.10.5 -lquadmath -L/usr/lib -lgfortran -lm > ExtUtils::F77: Validating -L/usr/lib/gcc/x86_64-pc-cygwin/4.9.3 > -lgcc_ext.10.5 -lgcc_s.10.5 -lquadmath -L/usr/lib -lgfortran -lm > ExtUtils::F77: Unable to find library -lgcc_ext.10.5 > ExtUtils::F77: Unable to find library -lgcc_s.10.5 > ExtUtils::F77: Unable to guess and/or validate system/compiler > configuration > ExtUtils::F77: Will try system=Generic Compiler=G77 > ExtUtils::F77: Well that didn't appear to validate. Well I will try it > anyway. > ExtUtils::F77: There does not appear to be any configuration info about > ExtUtils::F77: names with trailing underscores for system Generic. > Will assume > ExtUtils::F77: F77 names have trailing underscores. > ExtUtils::F77: There does not appear to be any configuration info about > ExtUtils::F77: the F77 compiler name. Will assume 'f77'. > ExtUtils::F77: Compiler: f77 > ExtUtils::F77: There does not appear to be any configuration info about > ExtUtils::F77: the options for the F77 compiler. Will assume none > ExtUtils::F77: necessary. > ExtUtils::F77: Cflags: > ok 1 > Use of uninitialized value $ExtUtils::F77::Runtime in concatenation > (.) or string at t/require.t line 17. > Can't exec "f77": No such file or directory at t/require.t line 28. > 2 WARNING: f77 -c hello.f returned non-zero exit status 255 > > > > On 11/14/2015 23:09, Karl Glazebrook wrote: >> Hi there PDL developers, >> >> I’d like to repeat my call for testing for EU::F77, my changes stop >> meltdowns with PERL_DL_NONLAZY=1 and should improve PDL test suite >> compliance: >> >>> I’ve made some improvements to the gfortran linking which should >>> avoid runtime unresolved symbols issues. (e.g. ‘make test’ with >>> modules like PGPLOT) >>> >>> It works on OS X, so various Linux tests would be appreciated. >>> Should be no difference on Win32 >>> >>> (Basically I figure that the extra libs needed apply to all versions >>> of gfortran > 4.9 and do not depend on OS… nice to confirm this!) >>> >> >> Please now get this from >> >> https://sourceforge.net/p/pdl/extutils-f77/ci/master/tree/ >> >> Branch is ‘better-gfortran-linking’ >> >> Assuming I have done the git magic right! >> >> best >> >> Karl >> >> >> >>> On 2 Nov 2015, at 10:15 am, Karl Glazebrook <karlglazebr...@mac.com> >>> wrote: >>> >>> >>> Ahh! >>> >>> Sorry I totally forgot this had been taken over by you last year Chris! >>> >>> Splendid. I will retrofit my changes in to the SF repository you made. >>> >>> Karl >>> > ------------------------------------------------------------------------------ _______________________________________________ pdl-devel mailing list pdl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pdl-devel
