Mail Archives: djgpp/1992/12/21/12:57:37
src4src!mcdhup!rutgers!acds.physik.rwth-aachen.de!kuku (Christoph Kukulies) writes:
> >Well, as long as you don't do any system calls, that is. :-)
>
> Hhmm. Explain. I think libm is self contained and whenever it should
> do a system call it will take the one from djgpp libc.a. Or am I wrong?
Well, system calls are encoded in the binary in a system dependent way...
I _don't_ mean calling a library routine that makes a system call, I mean
_being_ the routine that actually calls the OS. That is, of course, not
portable. Perhaps I was ambiguous... I was not commenting on libm.a, I
was commenting on binary compatibility.
E.g., you can't take the binary for write() and link it in with DJ's
stuff and expect it to do other than fault.
alane AT wozzle DOT linet DOT org (J. Alan Eldridge)
Fido: The University of Walamaloo 1:272/38.473
- Raw text -