From: Sylvain Kerjean <skerjean@irisa.fr>
To: caml-list@inria.fr
Subject: [Fwd: Re: [Caml-list] BeOS and Unix library problems]
Date: Mon, 12 Mar 2001 09:58:53 +0100 [thread overview]
Message-ID: <3AAC8FCD.B77A2671@irisa.fr> (raw)
Sébastien Pierre wrote:
> Looking at the sources, the "nice.c" and "chroot.c" source files both
> use calls to functions called "nice" and "chroot" which I can't find
> (and obviously the linker has the same problem ;)... Does anyone has
> any idea on how to solve this?
This problem is well known : these systems call are not implemented in
BeOS yet.
The only solution i know is to modify the sources of BeOS .....
So no chroot nor nice system calls for the moment.
PS : Sebastien, your mail address has permanent errors ...
--
Sylvain Kerjean
IRISA-INRIA, Campus de Beaulieu, 35042 Rennes cedex, France
Tél: +33 (0) 2 99 84 75 99, Fax: +33 (0) 2 99 84 71 71
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
reply other threads:[~2001-03-12 16:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AAC8FCD.B77A2671@irisa.fr \
--to=skerjean@irisa.fr \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).