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

Re: 950125: compiling on CRAY C90

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 950125: compiling on CRAY C90
  • Date: Wed, 25 Jan 95 09:29:14 -0700
>From: Ming Cai <address@hidden>
>Organization: University of Maryland
>Subject: Re: 950125: compiling on CRAY C90 
>Keywords: 199501202055.AA21596

In the above message you wrote:

>Hi,  I did "make" in the subdirectory lib/ sucessfully.
>Next I moved the subdirectory src/ and execute "make"
>
>here is the output I got.
>
>        cc -c -DHAVE_CONFIG_H -I.. -I. -I./../lib  -g ansi2knr.c
>        cc  -o ansi2knr ansi2knr.o
>        ./ansi2knr --varargs m4.c > m4._c
>cc -c -DHAVE_CONFIG_H -I.. -I. -I./../lib -g m4._c
>        ./ansi2knr --varargs builtin.c > builtin._c
>cc -c -DHAVE_CONFIG_H -I.. -I. -I./../lib -g builtin._c
>        ./ansi2knr --varargs debug.c > debug._c
>cc -c -DHAVE_CONFIG_H -I.. -I. -I./../lib -g debug._c
>cc-172 cc: WARNING File = debug.c, Line = 121
>  No code is generated for a superfluous expression.
>cc-106 cc: WARNING File = debug.c, Line = 230
>  The declaration of "va_dcl" has no type specifier.
>cc-491 cc: ERROR File = debug.c, Line = 230
>  In a function definition, "va_dcl" does not appear in the identifier list.
...

Unfortunately, because I don't have access to your build environment (a
CRAY C90) it's extremely difficult for me to comment constructively on
any problems you encounter. The only things I can suggest are

    1.  Try again from a clean slate, i.e.

        a.  Go to the top-level source directory.

        b.  Execute `make distclean'.

        c.  Execute `./configure --prefix=<whatever>'.

        d.  Execute `make'.

    2.  Contact the GNU m4 people and ask for their help.  The README file
        should have their email address.

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