20020822: building netCDF on Solaris/Intel using pgcc: ncx.c problem

Scott,

> To: address@hidden
> From: "Applequist, Dr. Scott" <address@hidden>
> Subject: compile problem with netCDF
> Organization: ?
> Keywords: 200208222016.g7MKGhK26868

The above message contained the following:

> This is probably my fault, but I cannot figure it out.
> The messages in the configure.log are scary, but I don't think they are the
> problem.  When I try to "make" I get the fatal errors.
> 
> Note, the "-tp p6" in the FFLAGS causes a Pentium III executable to be
> build.  This is a Xeon P4 machine using Solaris and if we don't do this
> certain functions (like INT()) cause the program to core.
> 
> Thank you for looking at it.
> Scott
> 
> applequs@acmes3:/data/home/applequs/netcdf-3.5.0/src>uname -a
> SunOS acmes3 5.8 Generic_108529-14 i86pc i386 i86pc
> 
> applequs@acmes3:/data/home/applequs/netcdf-3.5.0/src>more VERSION
> 3.5.0
> 
> applequs@acmes3:/data/home/applequs/netcdf-3.5.0/src>which pgf90
> /usr/pgi/solaris86/bin/pgf90
> applequs@acmes3:/data/home/applequs/netcdf-3.5.0/src>which pgcc
> /usr/pgi/solaris86/bin/pgcc
> applequs@acmes3:/data/home/applequs/netcdf-3.5.0/src>which pgCC
> /usr/pgi/solaris86/bin/pgCC
> ------------------------------------------------------------
> applequs@acmes3:/data/home/applequs/netcdf-3.5.0/src>cat configure.log
> creating cache ./config.cache
> checking for top-level source-directory
> /data/home/applequs/netcdf-3.5.0/src
> checking for m4 preprocessor
> checking for m4... m4
> checking m4 flags... -B10000
> checking C compiler "pgcc"... works
> checking how to make dependencies... cc -xM
> checking for pgCC... pgCC
> checking C++ compiler "pgCC"... works
> checking how to run the C preprocessor... pgcc -E
> checking user-defined Fortran-77 compiler "pgf90"... works
> checking for Fortran .F compiler... 
> checking if Fortran-77 compiler handles *.F files... yes
> checking "pgf90" as Fortran-90 compiler... works
> checking for nm utility
> checking for nm... nm
> checking nm flags... 
> checking for C-equivalent to Fortran routine "SUB"... sub_
> 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
> checking for Fortran-equivalent to netCDF "byte"... byte
> checking for Fortran-equivalent to netCDF "short"... integer*2
> checking for math library
> checking for tanh in -lc... yes
> checking for ar utility
> checking for ar... ar
> checking ar flags... cru
> checking for nm utility
> checking for nm... (cached) nm
> checking nm flags... 
> checking for ranlib... ranlib
> checking for stdlib.h... yes
> checking for sys/types.h... yes
> checking for strerror... yes
> checking for working ftruncate()... yes
> checking for working alloca.h... yes
> checking for alloca... yes
> checking for st_blksize in struct stat... yes
> 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... no
> checking whether byte ordering is bigendian... no
> 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 catman... catman
> checking for manual-page index command... catman -w -M $(MANDIR)
> checking binary distribution directory... /home/ftp/pub/binary/dummy_system
> updating cache ./config.cache
> creating ./config.status
> creating macros.make
> udcreating fortran/nfconfig.inc
> creating libsrc/ncconfig.h
...

> Making `all' in directory /data/home/applequs/netcdf-3.5.0/src/libsrc
> 
> pgcc -c -O -I.  -DNDEBUG attr.c
> pgcc -c -O -I.  -DNDEBUG dim.c
> pgcc -c -O -I.  -DNDEBUG error.c
> pgcc -c -O -I.  -DNDEBUG -DVERSION=`cat ../VERSION` libvers.c
> pgcc -c -O -I.  -DNDEBUG nc.c
> pgcc -c -O -I.  -DNDEBUG ncio.c
> pgcc -c -O -I.  -DNDEBUG ncx.c
> Assembler: ncx.c
>         "/var/tmp/pgccAAAvsaOpl.s", line 880 : Illegal mnemonic
>         "/var/tmp/pgccAAAvsaOpl.s", line 880 : Syntax error
>         "/var/tmp/pgccAAAvsaOpl.s", line 1506 : Illegal mnemonic
>         "/var/tmp/pgccAAAvsaOpl.s", line 1506 : Syntax error
>         "/var/tmp/pgccAAAvsaOpl.s", line 2317 : Illegal mnemonic
>         "/var/tmp/pgccAAAvsaOpl.s", line 2317 : Syntax error
>         "/var/tmp/pgccAAAvsaOpl.s", line 2439 : Illegal mnemonic
>         "/var/tmp/pgccAAAvsaOpl.s", line 2439 : Syntax error
>         "/var/tmp/pgccAAAvsaOpl.s", line 2496 : Illegal mnemonic
>         "/var/tmp/pgccAAAvsaOpl.s", line 2496 : Syntax error
>         "/var/tmp/pgccAAAvsaOpl.s", line 2553 : Illegal mnemonic
>         "/var/tmp/pgccAAAvsaOpl.s", line 2553 : Syntax error
>         "/var/tmp/pgccAAAvsaOpl.s", line 4390 : Illegal mnemonic
>         "/var/tmp/pgccAAAvsaOpl.s", line 4390 : Syntax error
>         "/var/tmp/pgccAAAvsaOpl.s", line 5029 : Illegal mnemonic
>         "/var/tmp/pgccAAAvsaOpl.s", line 5029 : Syntax error

This is a problem.  We don't have access to a Solaris for Intel system
with Portland Group compilers -- so we can't duplicate the problem.
You could send me file "/var/tmp/pgccAAAvsaOpl.s which, I assume, is an
assembly language version of file "libsrc/ncx.c" -- but I wouldn't know
how to interpret it.

Is there some way that you could get pgcc to refer to the C code?

Alternatively, can you use a different C compiler?

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