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

Re: 19991013: building Netcdf 3.4: bad SunOS 5.5.1 build environment

Pedro,

> To: address@hidden
> From: NAVARRO PEDRO <address@hidden>
> Subject: Netcdf 3.4 help
> Organization: The University of Greenwich
> Keywords: 199910130949.DAA26848

In the above message, you wrote:

> I am trying to compile the netcdf package (version 3.4) but I am 
> having problems. I would be very grateful if I could get some help 
> from you.
> 
> As specified in the netcdf documentation I am sending the following 
> information:
> 
> A. The standard output of the command 'uname -a' is:
>      SunOS gis1 5.5.1 Generic_103640 sun4u sparc SUNW, ultra-1
> 
> B. The contents of the file VERSION is: 3.4
> 
> C. The pathname of the compilers:
>     (Fortran): /home5/fortran/SUNWspro/bin/f90
>     ( C )        : /home5/C5.0/SUNWspro/SC5.0/bin/cc
>     (C++)    : /home5/C5.0/SUNWspro/SC5.0/bin/CC
> 
> D. The contents of file configure.log (attached)

The attachment was actually the file "config.log" rather than the file
"configure.log" mentioned in step 6 near the end of the INSTALL file.

> 
> E. I am also sending the screen output when running the configure 
> script (output.scr, attached)

This is actually the file "configure.log".  This file is often
confused with "config.log".

> 
> Many thanks,
> 
> Pedro Navarro
> University of Greenwich
> Natural resources Institute
> Chatham Maritime
> United Kingdom
...

> Content-description: Text from file 'CONFIG.LOG'
> 
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> configure:1020: cc -c -g  conftest.c 1>&5
> configure:1153: CC -c   conftest.C 1>&5
> CC: Cannot find /home5/C5.0/SUNWspro/SC5.0/bin/fbe

The last line above indicates that your C++ development environment
is broken.  If you want the C++ netCDF interface, then you'll have to
correct this situation before attempting to build the netCDF package.  I
suggest trying the C++ compiler on small test programs to uncover the
problem and consulting with your system administrator.

> configure:1220: cc -E  conftest.c >/dev/null 2>conftest.out
> configure:1319: f90 -c -g conftest.f
> configure:1422: f90 -o conftest -g conftest.F  
> configure:1463: f90 -c -g conftest.f
> configure:1498: f90 -c -g conftest.f
> 
>       byte value
>                 ^
> "conftest.f", Line = 2, Column = 17: ERROR: Unknown statement.  Expected 
> assignment statement but found "EOS" instead of "=" or "=>".
> 
> f90: COMPILE TIME 0.040000 SECONDS
> f90: MAXIMUM FIELD LENGTH 1738108 DECIMAL WORDS
> f90: 3 SOURCE LINES
> f90: 1 ERRORS, 0 WARNINGS, 0 OTHER MESSAGES, 0 ANSI
> f90: CODE: 0 WORDS, DATA: 0 WORDS
> configure:1498: f90 -c -g conftest.f
> configure:1521: f90 -c -g conftest.f
> configure:1555: cc -c  -g conftest.c
> configure:1557: f90 -g -c conftestf.f
> configure:1559: f90 -o conftest -g  conftestf.o conftest.o 
> configure:1561: ./conftest
> configure:1602: cc -c  -g conftest.c
> configure:1604: f90 -g -c conftestf.f
> configure:1606: f90 -o conftest -g  conftestf.o conftest.o 
> configure:1608: ./conftest
> configure:1649: cc -c  -g conftest.c
> configure:1651: f90 -g -c conftestf.f
> configure:1653: f90 -o conftest -g  conftestf.o conftest.o 
> configure:1655: ./conftest
> configure:1696: cc -c  -g conftest.c
> configure:1698: f90 -g -c conftestf.f
> configure:1700: f90 -o conftest -g  conftestf.o conftest.o 
> configure:1702: ./conftest
> configure:1747: cc -c  -g conftest.c
> configure:1749: f90 -g -c conftestf.f
> configure:1751: f90 -o conftest -g  conftestf.o conftest.o 
> configure:1753: ./conftest
> configure:1794: cc -c  -g conftest.c
> configure:1796: f90 -g -c conftestf.f
> configure:1798: f90 -o conftest -g  conftestf.o conftest.o 
> configure:1800: ./conftest
> configure:1841: cc -c  -g conftest.c
> configure:1843: f90 -g -c conftestf.f
> configure:1845: f90 -o conftest -g  conftestf.o conftest.o 
> configure:1847: ./conftest
> configure:1890: cc -c  -g conftest.c
> configure:1892: f90 -g -c conftestf.f
> configure:1894: f90 -o conftest -g  conftestf.o conftest.o 
> configure:1896: ./conftest
> configure:1937: cc -c  -g conftest.c
> configure:1939: f90 -g -c conftestf.f
> configure:1941: f90 -o conftest -g  conftestf.o conftest.o 
> configure:1943: ./conftest
> configure:1984: cc -c  -g conftest.c
> configure:1986: f90 -g -c conftestf.f
> configure:1988: f90 -o conftest -g  conftestf.o conftest.o 
> configure:1990: ./conftest
> configure:2023: f90 -c -g conftest.f
> 
>                byte foo
>                        ^
> "conftest.f", Line = 1, Column = 24: ERROR: Unknown statement.  Expected 
> assignment statement but found "EOS" instead of "=" or "=>".
> 
> f90: COMPILE TIME 0.050000 SECONDS
> f90: MAXIMUM FIELD LENGTH 1738108 DECIMAL WORDS
> f90: 2 SOURCE LINES
f90: 1 ERRORS, 0 WARNINGS, 0 OTHER MESSAGES, 0 ANSI
> f90: CODE: 0 WORDS, DATA: 0 WORDS
> configure:2023: f90 -c -g conftest.f
> configure:2044: f90 -c -g conftest.f
> configure:2084: cc -o conftest -g   conftest.c -lc   1>&5
> ld: fatal: file /home5/C5.0/SUNWspro/SC5.0/lib/crti.o: cannot open file; 
> errno=2
> ld: fatal: file /home5/C5.0/SUNWspro/SC5.0/lib/crt1.o: cannot open file; 
> errno=2
> ld: fatal: file /home5/C5.0/SUNWspro/SC5.0/lib/values-xa.o: cannot open file; 
> errno=2
> ld: fatal: file /home5/C5.0/SUNWspro/SC5.0/lib/crtn.o: cannot open file; 
> errno=2
> ld: fatal: File processing errors.  No output written to conftest
> configure:2118: cc -o conftest -g   conftest.c -lm   1>&5
> ld: fatal: file /home5/C5.0/SUNWspro/SC5.0/lib/crti.o: cannot open file; 
> errno=2
> ld: fatal: file /home5/C5.0/SUNWspro/SC5.0/lib/crt1.o: cannot open file; 
> errno=2
> ld: fatal: file /home5/C5.0/SUNWspro/SC5.0/lib/values-xa.o: cannot open file; 
> errno=2
> ld: fatal: file /home5/C5.0/SUNWspro/SC5.0/lib/crtn.o: cannot open file; 
> errno=2
> ld: fatal: File processing errors.  No output written to conftest

The error messages above indicate that your C development environment is
broken.  You'll have to correct this situation before you can build the
netCDF package.  I suggest trying the C compiler on small test programs
to uncover the problem and consulting with your system administrator.

When you've corrected your development environment and wish to retry
building the netCDF package, then perform steps 2 through 9 near the end
of the INSTALL file.

Please let me know if this helps.

--------
Steve Emmerson   <http://www.unidata.ucar.edu>