Martin Spott wrote:
Hello, would anyone mind having a look at this one:
make: Entering directory `/usr/local/src/FlightGear/src/Network'
CC -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
-I/opt/include -I/usr/freeware/include -Xcpluscomm
-I/opt/FlightGear/include -I/usr/local//include -O2 -use_readonly_const
-rdata_shared -woff 1001,1012,1014,1110,1116,1155,1172,1174,1234,1401
-LANG:exceptions=ON -I/opt/include -I/usr/freeware/include -Wl,-rpath
-Wl,/usr/freeware/lib32 -Wl,-rpath -Wl,. -I/opt/FlightGear/include/simgear/compatibility -D_REENTRANT -c -o
ATC-Inputs.o `test -f 'ATC-Inputs.cxx' || echo './'`ATC-Inputs.cxx
cc-1020 CC: ERROR File = ATC-Inputs.cxx, Line = 72
The identifier "lseek" is undefined.
lseek( fd, 0, SEEK_SET ); ^
cc-1020 CC: ERROR File = ATC-Inputs.cxx, Line = 74 The identifier "read" is undefined.
int result = read( fd, analog_in_bytes, ATC_ANAL_IN_BYTES ); ^ [... and so on ...]
My first stab would be to run "man lseek" and "man read" on your platform (sun/sgi?) to see what includes you need to have to use these functions. Or you could just add your platform to the list that skips compiling this section of code ... at the moment it's designed to communicate with a linux /proc device driver, and as far as I know (I wrote the driver) it hasn't been ported to any other platforms or OS's.
Curtis Olson http://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
_______________________________________________ Flightgear-devel mailing list Flightgearemail@example.com http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d