> I think what's happening is, NetBSD is mistaking the executable for a
> real NetBSD executable.  Most of the syscalls appear compatible, but
> I'd offer a small wager that the Linux syscall number for mmap is the
> same as the NetBSD syscalls number for dup2.  

You're right. This must be why it does not work.

> Get NetBSD to recognize it as a Linux executable and I feel sure the
> dup2 problem will vanish.

Ok, so now the question is: how LinuxPPC statically linked programms
differ from LinuxPPC dynamically linked programs? Anyone has some
information about this?

-- 
Emmanuel Dreyfus.
p99dreyf@criens.u-psud.fr