This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: Where to implement fork()
- From: Joel Sherrill <joel dot sherrill at oarcorp dot com>
- To: Christian Haake <chaake at mailbox dot tu-berlin dot de>
- Cc: "newlib at sourceware dot org" <newlib at sourceware dot org>
- Date: Mon, 9 Jul 2012 14:53:12 -0500
- Subject: Re: Where to implement fork()
- References: <4FFB2F98.90206@mailbox.tu-berlin.de>
On 07/09/2012 02:23 PM, Christian Haake wrote:
Hi,
while implementing newlib stubs I'm wondering where I should implement
fork().
I successfully implemented _sbrk in
<pathtonewlib>/newlib/libc/sys/arm/syscalls.c but there is no function
stub called _fork(void)
Or can I simply add this function stub into this file?!?
Can anybody give me a hint?
I suspect you are adding bare board specific code. This would
go in libgloss where there are already a number of stubs
for fork() and other methods.
IMO there are some unfortunately named directories in libc/sys which
appear to be generic CPU support but they are really for specific
"systems." The sys/arm directory is questionably named because
it is really support for the ARM Angel/RDI monitor. Mostly a
confusing historical artifact at this point.
Thanks in advance...
Chris
--
Joel Sherrill, Ph.D. Director of Research& Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985