[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: make finished.. make test failed
- Subject: Re: make finished.. make test failed
- Date: Thu, 13 Dec 2001 10:22:17 -0700
>To: address@hidden
>From: Dierk Polzin <address@hidden>
>Subject: Re: 20011213: make finished.. make test failed
>Organization: Center for Sustainability and Global Environment/U Wisconsin
>Keywords: 200111161613.fAGGDvN05779, MacOS X, absoft, cfortran.h
Dierk
> MAKE TEST FAILS here... should I worry about this?
>
>
> FORTRAN 77 Compiler 7.0a, Copyright (c) 1987-2001, Absoft Corp.
> /usr/bin/cc -c -O -Df2cFortran fortlib.c
> /Applications/Absoft/bin/f77 -o nf_test -N15 -f -w test_get.o
> test_put.o nf_error.o nf_test.o test_read.o test_write.o util.o
> fortlib.o ../libsrc/libnetcdf.a
> /usr/bin/ld: Undefined symbols:
> _nf_close_
> _nf_get_att_double_
> _nf_get_att_int1_
> ....ETC...ETC....
> _nf_rename_dim_
> _nf_rename_var_
> _nf_set_fill_
> _nf_sync_
>
> make[2]: *** [nf_test] Error 1
> make[1]: *** [subdir_target] Error 1
> make: *** [nf_test/test] Error 2
>
> Somewhere else
This is a problem if you want to use the Fortran-77 or Fortran90
interfaces.
I think you should not be using the
CPPFLAGS=-Df2cFortran
for Absoft Fortran compilers. It's intended for f2c or g77, to
specify their Fortran to C calling conventions for cfortran.h, but the
Absoft compilers use different conventions. So I recommend you try
unsetting the CPPFLAGS environment variable, removing the
"config.cache" file, doing a ",make clean", then running the
"configure" script again with all the other environment variable
settings you have.
--Russ