NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

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

20021016: building netcdf-3.5.1-beta3 with gcc-3.2: stdin not constant

Juergen,

> To: address@hidden
> From: Juergen Rose <address@hidden>
> Subject: Can't configure and compile netcdf-3.5.1-beta3 with gcc-3.2
> Organization: ?

The above message contained the following:

> following the hints in .../netcdf-3.5.1-beta3/src/INSTALL.html my system
> has the following properties:
> 
> A. Linux vilm 2.4.20-pre7 
> 
> B. 3.5.1-beta3
> 
> C. gcc is /usr/bin/gcc
>    g77 is /usr/bin/g77
>    g++ is /usr/bin/g++
...

> make[2]: Entering directory
> `/usr/src_vilm/Libs/netcdf-3.5.1-beta3/src/ncgen'
> /usr/bin/gcc -c -g -I../libsrc -I.  -Df2cFortran main.c
> /usr/bin/gcc -c -g -I../libsrc -I.  -Df2cFortran load.c
> /usr/bin/gcc -c -g -I../libsrc -I.  -Df2cFortran ncgentab.c
> In file included from ncgen.y:824:
> ncgenyy.c:75: initializer element is not constant
> ncgenyy.c:75: (near initialization for `yyin')
> ncgenyy.c:75: initializer element is not constant
> ncgenyy.c:75: (near initialization for `yyout')
> make[2]: *** [ncgentab.o] Error 1
> 
> This comes, because in newer versions of gcc or glibc stdin and stdout
> are not constant, that's why it is not possible to initialize global
> FILE pointer with them.
> I would appreciate any hint.

I'll need more information in order to diagnose the problem.
Specifically, I need to see exactly what is causing the problem. Would
you please do the following:

    1.  Go into the "ncgen/" subdirectory.

    2.  Execute the following command:

            /usr/bin/gcc -E -I../libsrc -I. -Df2cFortran ncgentab.c > ncgentab.i

    3.  Send me the output from the following command:

            /usr/bin/gcc -c ncgentab.i

    4.  Send me the relevant lines in the file "ncgentab.i" according
        to the error messages of the above command.

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