Messages in this thread | ![/](/images/icornerl.gif) | | Date | Thu, 26 Jun 2008 10:02:02 -0700 | From | "H. Peter Anvin" <> | Subject | Re: [PATCH 59/60] microblaze_v4: syscall_table.S and unistd.h |
| |
Arnd Bergmann wrote: > > You still set __NR_fork. There is no point defining the number if you > can't actually call the syscall in the first place. >
Worse, it is actively *harmful* to set the number; klibc or anything that uses similar kinds of scripts for portability will see the symbol and think the system call is available.
-hpa
| ![\](/images/icornerr.gif) |