[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

970610: building using NAG f90

Steve,

>Date: 10 Jun 1997 13:42:37 -0500 
>From: "Steve Mauget" <address@hidden>
>Organization: USDA
>To: "Steve Emmerson" <address@hidden>
>Subject: Re: 970610: building using N 
>Keywords: 199706021417.IAA27579

In the above message, you wrote:

>         Did you get my last message regarding a possible fix to my
> problem?

Yes.  I just replied.

>         In answer to the question:
>
>                    Does your netcdf data loader program call NCVPT
>                    with both INTEGER*1 and INTEGER*2 datatypes in the
>                    same compilation unit?
> 
>        the answer is no.

This might be why the NAG f90 compiler didn't complain about compiling
your program.

>        Enclosed here is standard out & err to configure , with
> config.log appended. Since I have no way of knowing if the "***"
> lines and error messages are worth bothering about I await your
> instructions.
> 
>                                                                               
>                                       Steve M.
> 
> 
> creating cache ./config.cache
> checking for m4... m4
> checking user-defined C compiler "/bin/c89"
> checking C compiler... works
> checking for how to make dependencies... cc -M
> configure: warning: Empty CXX variable
> configure: warning: The C++ interface will not be built
> checking how to run the C preprocessor... /bin/c89 -E
> checking user-defined FORTRAN compiler "/usr/local/bin/f90"... works
> checking if FORTRAN compiler handles *.F files... no
> checking for FORTRAN preprocessor... /bin/c89 -E
> checking for C-equivalent to FORTRAN routine "SUB"... sub_
> checking for FORTRAN "byte"... no
> checking for FORTRAN "integer*1"... yes
> checking for FORTRAN "integer*2"... yes
> checking if FORTRAN "integer*1" is C "signed char"... yes
> checking if FORTRAN "integer*1" is C "short"... no
> ***checking if FORTRAN "integer*1" is C "int"... no

The above merely indicates that a Fortran "integer*1" datatype is not
the same as a C "int" datatype.  This is not a problem.  It's merely
somthing that the netCDF package has to accomodate.

> checking if FORTRAN "integer*2" is C "short"... yes
> ***checking if FORTRAN "integer*2" is C "int"... no

Ditto for the above types.

> checking if FORTRAN "integer" is C "int"... yes
> checking if FORTRAN "real" is C "float"... yes
> checking if FORTRAN "doubleprecision" is C "double"... yes
> checking for FORTRAN-equivalent to netCDF "byte"... integer*1
> checking for FORTRAN-equivalent to netCDF "short"... integer*2
> checking for math library
> checking for -lc... no
> checking for -lm... yes
> checking for ar... ar
> checking for ranlib... :
> checking for stdlib.h... yes
> checking for sys/types.h... yes
> checking for strerror... yes
> checking for ftruncate... yes
> checking for st_blksize in struct stat... yes
> checking whether cross-compiling... no
> checking for IEEE floating point format... yes
> checking for ANSI C header files... yes
> checking for size_t... yes
> checking for off_t... yes
> checking for ssize_t... yes
> checking for ptrdiff_t... yes
> checking for uchar... no
> checking whether char is unsigned... yes
> checking whether byte ordering is bigendian... yes
> checking size of short... 2
> checking size of int... 4
> checking size of long... 4
> checking size of float... 4
> checking size of double... 8
> checking size of off_t... 4
> checking size of size_t... 4
> checking for manual-page index command... 
> checking binary distribution directory... /home/ftp/pub/binary/dummy_system
> updating cache ./config.cache
> creating ./config.status
> creating macros.make
> udcreating fortran/netcdf-cpp.inc
> creating libsrc/ncconfig.h
> libsrc/ncconfig.h is unchanged
> 
> C*******************************************************************************
> 
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> configure:1016: /bin/c89 -c -g  conftest.c 1>&5
> configure:1216: /bin/c89 -E  conftest.c >/dev/null 2>conftest.out
> configure:1315: /usr/local/bin/f90 -c -g conftest.f
> configure:1410: /usr/local/bin/f90 -o conftest -g conftest.F  
> File with unknown suffix .F passed to ld
> cc: Error: Fortran is not installed (could not find /usr/lib/fcom).
> configure:1445: /usr/local/bin/f90 -c -g conftest.f
> configure:1480: /usr/local/bin/f90 -c -g conftest.f
> Error: conftest.f, line 2: Unrecognised statement
> Error: conftest.f, line 2: syntax error
> ***Malformed statement
> Warning: conftest.f, line 3: Unused dummy argument VALUE
>          detected at END@<end-of-statement>
> [f90 terminated - errors found by pass 1]
> configure:1480: /usr/local/bin/f90 -c -g conftest.f
> Extension: conftest.f, line 2: Byte count on numeric data type
>            detected at *@1
> Warning: conftest.f, line 3: Unused dummy argument VALUE
>          detected at END@<end-of-statement>
> [f90 continuing despite warning messages]
> configure:1503: /usr/local/bin/f90 -c -g conftest.f
> Extension: conftest.f, line 2: Byte count on numeric data type
>            detected at *@2
> Warning: conftest.f, line 3: Unused dummy argument VALUE
>          detected at END@<end-of-statement>
> [f90 continuing despite warning messages]
> configure:1537: /bin/c89 -c  -g conftest.c
> configure:1539: /usr/local/bin/f90 -o conftest -g  conftestf.f conftest.o 
> Extension: conftestf.f, line 1: Byte count on numeric data type
>            detected at *@1
> [f90 continuing despite warning messages]
> ld: WARNING 84: /usr/lib/libm.so is not used for resolving any symbol.
> configure:1541: ./conftest
> configure:1579: /bin/c89 -c  -g conftest.c
> configure:1581: /usr/local/bin/f90 -o conftest -g  conftestf.f conftest.o 
> Extension: conftestf.f, line 1: Byte count on numeric data type
>            detected at *@1
> [f90 continuing despite warning messages]
> ld: WARNING 84: /usr/lib/libm.so is not used for resolving any symbol.
> configure:1583: ./conftest
> configure:1621: /bin/c89 -c  -g conftest.c
> configure:1623: /usr/local/bin/f90 -o conftest -g  conftestf.f conftest.o 
> Extension: conftestf.f, line 1: Byte count on numeric data type
>            detected at *@1
> [f90 continuing despite warning messages]
> ld: WARNING 84: /usr/lib/libm.so is not used for resolving any symbol.
> configure:1625: ./conftest
> configure:1667: /bin/c89 -c  -g conftest.c
> configure:1669: /usr/local/bin/f90 -o conftest -g  conftestf.f conftest.o 
> Extension: conftestf.f, line 1: Byte count on numeric data type
>            detected at *@2
> [f90 continuing despite warning messages]
> ld: WARNING 84: /usr/lib/libm.so is not used for resolving any symbol.
> configure:1671: ./conftest
> configure:1709: /bin/c89 -c  -g conftest.c
> configure:1711: /usr/local/bin/f90 -o conftest -g  conftestf.f conftest.o 
> Extension: conftestf.f, line 1: Byte count on numeric data type
>            detected at *@2
> [f90 continuing despite warning messages]
> ld: WARNING 84: /usr/lib/libm.so is not used for resolving any symbol.
> configure:1713: ./conftest
> configure:1753: /bin/c89 -c  -g conftest.c
> configure:1755: /usr/local/bin/f90 -o conftest -g  conftestf.f conftest.o 
> ld: WARNING 84: /usr/lib/libm.so is not used for resolving any symbol.
> configure:1757: ./conftest
> configure:1795: /bin/c89 -c  -g conftest.c
> configure:1797: /usr/local/bin/f90 -o conftest -g  conftestf.f conftest.o 
> ld: WARNING 84: /usr/lib/libm.so is not used for resolving any symbol.
> configure:1799: ./conftest
> configure:1837: /bin/c89 -c  -g conftest.c
> configure:1839: /usr/local/bin/f90 -o conftest -g  conftestf.f conftest.o 
> ld: WARNING 84: /usr/lib/libm.so is not used for resolving any symbol.
> configure:1841: ./conftest
> configure:1871: /usr/local/bin/f90 -c -g conftest.f
> Error: conftest.f, line 1: Unrecognised statement
> Error: conftest.f, line 1: syntax error
> ***Malformed statement
> [f90 terminated - errors found by pass 1]
> configure:1871: /usr/local/bin/f90 -c -g conftest.f
> Extension: conftest.f, line 1: Byte count on numeric data type
>            detected at *@1
> Warning: conftest.f, line 2: Unused symbol FOO
>          detected at END@<end-of-statement>
> [f90 continuing despite warning messages]
> configure:1892: /usr/local/bin/f90 -c -g conftest.f
> Extension: conftest.f, line 1: Byte count on numeric data type
>            detected at *@2
> Warning: conftest.f, line 2: Unused symbol FOO
>          detected at END@<end-of-statement>
> [f90 continuing despite warning messages]
> configure:1932: /bin/c89 -o conftest -g   conftest.c -lc   1>&5
> ld: ERROR 33: Unresolved text symbol "tanh" -- 1st referenced by conftest.o.
> ld: INFO 60: Output file removed because of error.
> configure:1966: /bin/c89 -o conftest -g   conftest.c -lm   1>&5
> configure:2061: /bin/c89 -E  conftest.c >/dev/null 2>conftest.out
> configure:2095: /bin/c89 -E  conftest.c >/dev/null 2>conftest.out
> configure:2145: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2193: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2227: /bin/c89 -c -g  conftest.c 1>&5
> configure:2259: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2311: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2340: /bin/c89 -E  conftest.c >/dev/null 2>conftest.out
> configure:2405: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2623: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2661: /bin/c89 -c -g  conftest.c 1>&5
> cfe: Error: configure, line 2656: Syntax Error
>   bogus endian macros
>  -------^
> configure:2707: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2745: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2779: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2813: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2847: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2881: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2919: /bin/c89 -o conftest -g   conftest.c  1>&5
> configure:2957: /bin/c89 -o conftest -g   conftest.c  1>&5

The file "config.log" is expected to contain errors.  The utilities
that the configure script uses to determine the characteristics of your
system have their standard error redirected to it.  If the standard
output and standard error of the configure script don't indicate a
problem, then the "config.log" may safely be ignored.  (Granted, knowing
when the configure script indicates a problem is somewhat a matter of
experience :-).

So far, so good.  Now, try the following:

    1.  Execute the command "make clean".

    2.  Execute the command "make".
        Redirect standard output and standard error to a file.
        If this step fails, then send me the file and stop.

    3.  Execute the command "make test".
        Redirect standard output and standard error to a file.
        If this step fails, then send me the file and stop.

    4.  Execute the command "make install".
        Redirect standard output and standard error to a file.
        If this step fails, then send me the file and stop.

    5.  Execute the command "make clean".

--------
Steve Emmerson   <address@hidden>