This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 4.3 regression with netcdf library


checking if Fortran "integer" is C "int"... no

This in itself is highly suspicious. It means that either a) the binaries that you have are utterly, helplessly broken, as I don't think we could even have a quarter of our runtime testsuite passing if it were the case, or b) that the configure script can't really run the compiler. It think you might have installed the compiler in a non- standard location and not set LD_LIBRARY_PATH, for example. What happens when you run the compiler yourself, on a hello-world code?



Thanks, FX

PS: I've just tested with a recent gfortran, and it indeed goes well:

checking for Fortran "byte"... yes
checking for Fortran "integer*2"... yes
checking if Fortran "byte" is C "signed char"... yes
checking if Fortran "byte" is C "short"... no
checking if Fortran "byte" is C "int"... no
checking if Fortran "byte" is C "long"... no
checking if Fortran "integer*2" is C "short"... yes
checking if Fortran "integer*2" is C "int"... no
checking if Fortran "integer*2" is C "long"... no
checking if Fortran "integer" is C "int"... yes
checking if Fortran "real" is C "float"... yes
checking if Fortran "doubleprecision" is C "double"... yes


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]