normally whatever's passed to execve(2). I was just trying to point out
that some old Unixes, Xenix? -- I can't remember, effectively strip any
path, absolute or relative, from execve's argument before it turns up in
argv[0], i.e. execve("./ls", ...) and execve("/bin/ls", ...) both
deliver an argv[0] of "ls". Horrible, I know, but I remember getting
bit by it.
Must be because it was a Microsoft product. Luckily it is very difficult to find a Xenix system now.
Unless you are writing very important software that everyone needs in order to get anything done, I wouldn't worry about portability to Xenix or any other relic OS.
Bob ====================================== Bob Friesenhahn bfriesen@xxxxxxxxxxxxxxxxxxx http://www.simplesystems.org/users/bfriesen
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
