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.
Frank, > To: Unidata Support <address@hidden> > From: "Frank Colby" <address@hidden> > Subject: source compilation of 6.2.1 > Organization: UMass Lowell > Keywords: 200503162037.j2GKbav2009381 The above message contained the following: [snip] > Making `all' in directory /usr/local/ldm/ldm-6.2.1/src/misc > > /usr/bin/gcc -c -O -DNDEBUG -I.. -I../config -I../ulog error.c > /usr/bin/gcc -c -O -DNDEBUG -I.. -I../config -I../ulog fdnb.c > /usr/bin/gcc -c -O -DNDEBUG -I.. -I../config -I../ulog fsStats.c > fsStats.c: In function `fsStats': > fsStats.c:65: error: `STRUCT_STATFS' undeclared (first use in this function) > fsStats.c:65: error: (Each undeclared identifier is reported only once > fsStats.c:65: error: for each function it appears in.) > fsStats.c:65: error: parse error before "sbuf" > fsStats.c:68: error: `sbuf' undeclared (first use in this function) > *** Error code 1 Do any of the following header files define the structure "statfs": sys/stat.h, sys/param.h, and sys/mount.h? You can determine this via the following: $ cat >foo.c #include <sys/stat.h> #include <sys/param.h> #include <sys/mount.h> $ cc -E foo.c | grep statfs If so, then is there a feature-test macro (e.g., "__netbsd") that can be used to distinguish this case? Regards, Steve Emmerson