How do I get the error code for fpStat() ?

The oldlinux.stat() function returns FALSE on failure, and sets LinuxError.

The libc.stat() function returns (-1) on failure, and sets errno.

The baseunix.fpStat() function returns (-1) on failure, but it does not set LinuxError.

If I call fpStat() on a non-existing file, "strace" shows the error is ENOENT, but LinuxError is still zero.

( I am using 1.9.0 [2003/11/05] for i386/Linux )

program stat_test;
uses unix, baseunix, errors;
var
  info: stat;
  err: LongInt;
const
  fn = 'nosuch.file';
begin
  err:=fpStat(fn, info);
  if ( err  0 ) then
  begin
    pError(fn, LinuxError); // Success ?
    pError('Error', err); // (-1) ?
  end;
end.

__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree

LinuxError is already removed. Use errno instead, just like C.

LinuxError is legacy, and belongs to oldlinux only. This unit is provided for 1.0.x legacy only, and I strongly advise you against using it. Unit oldlinux is also linux/i386 only.

Baseunix follows POSIX conventions, and sets an internal errno on error and signals the errorcondition using the returnvalue (usually by returning -1, but some calls returning a type different from cint return something else. See manpages).

Because the BaseUnix internal errno is threadsafe, access is provided via functions, (BaseUnix.) fpseterrno and fpgeterrno.

So there are now three errorvariables:

1 oldlinux.linuxerror for calls in unit oldlinux only. _LEGACY_ 2 baseunix.fpgeterrno for all units that import unit syscall. (including unix and baseunix, but also sockets, ipc etc)
3 libc's errno (exposed in units that link to libc. Access to this variable in a threadsafe manner still has to be centralised in some unit, and all importing units adapted.

The idea of this is to have only two vars, instead of all the vars in all the units. One, internal for FPC's own syscalls, and one for C libc.

In the case that the FPC rtl is implemented on top of libc, (like planned for the future Mac OS X port), both point to the same internally, but the usercode needs no changing.

Internal Errno is only visible in implementation of system unit.

Use baseunix.geterrno/seterrno.