This is the mail archive of the
newlib@sources.redhat.com
mailing list for the newlib project.
Re: [RFC]: Provide IEEE 1003.1-2003 ulimit()
- From: Jeff Johnston <jjohnstn at redhat dot com>
- To: Nicholas Wourms <nwourms at netscape dot net>
- Cc: newlib at sources dot redhat dot com
- Date: Mon, 22 Dec 2003 15:59:26 -0500
- Subject: Re: [RFC]: Provide IEEE 1003.1-2003 ulimit()
- References: <bs259k$nqu$1@sea.gmane.org>
Nicholas,
This sounds similar to the other BSD submission you made. If your
code requires any BSD-specific syscalls or interfaces (i.e. any
syscall/interface that is not part of the generic newlib), then the code
must be put in sys/bsd. You will have to create this directory. This
is along the lines of sys/linux. Newlib is designed to work for
embedded platforms, most without an OS. An example of an exception to
the rule is the 64-bit I/O routines that are shared among a number of
systems that have 64-bit syscalls. It is configurable and is needed to
coexist properly with the regular I/O routines.
-- Jeff J.
Nicholas Wourms wrote:
Hi Jay,
I've got a working version of ulimit which I ported from FreeBSD. It
is fully compliant and inline with the SUSv3 standard. However, this
function, like quite a few others, are typically found in the "gen"
subdir of all the *BSD libc's. It makes no sense cluttering up the
stdio/stlib dirs with excessive files when it is clear that other
libc's have neatly stowed functions like these in the gen dir. I
await your comments before submitting my patch.
Cheers,
Nicholas