Double definition of errno?
Mon Aug 19 18:12:00 GMT 2002
On Mon, Aug 19, 2002 at 08:42:24PM +0200, KJK::Hyperion wrote:
>>Regarding your plans to change errno in the reentrant syscalls, this is
>>going to break a bunch of code because there are multiple reentrant
>>routines in newlib that directly access the reentrancy struct errno. This
>>means that your new errno won't be set in many instances.
>I didn't mean this. The "true" system calls won't set errno, they will
>return it as return value. It's much simpler this way, for a number of
>reasons. The system calls actually exposed to the code will be simple
>library calls encapsulating the "true" system calls, so they will be able
>to access the reentrancy structure
Sounds a little like the way linux does things, IIRC.
More information about the Newlib