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.
Charles, >Date: Mon, 15 Apr 1996 17:03:29 -0600 >From: Russ Rew <address@hidden> >To: address@hidden (Charles Packer) >Subject: Re: 960415: Bad test result under Ultrix >Keywords: 199604152011.AA25912 In the above message, Charles wrote: > > *> make test > > > > making `test' in directory /usr/users/packer/netc/src/xdr > > > > gcc -c -O -I/usr/include/rpc -std -Dconst= xdrtest.c > > gcc: unrecognized option `-std' > > gcc -o xdrtest -O xdrtest.o xdr.o xdrfloat.o xdrstdio.o xdrarray.o > > ./xdrtest > xdrtest_out.new > > diff xdrtest_out.new testout.sav > > *** XDR passes formatted test *** > > cmp test.xdr test_xdr.sav > > test.xdr test_xdr.sav differ: char 3477, line 1 > > *** XDR fails binary test *** > > *** Error code 1 gcc(1) wouldn't understand the `-std' option: only the DEC C compiler would. The configure script in the released package will add that option to CFLAGS if and only if the C compiler is `cc' (it isn't) and the CPU is a VAX (possible). I suspect that something else is afoot, e.g. the variable CFLAGS is defined in the environment or in in the CUSTOMIZE file as containing `-std'. -------- Steve Emmerson <address@hidden>