caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <xleroy@pauillac.inria.fr>
To: Vincent Barichard <barichar@info.univ-angers.fr>
Cc: CAML-LIST <caml-list@pauillac.inria.fr>
Subject: Re: [Caml-list] ocaml and beos
Date: Tue, 1 Oct 2002 14:45:36 +0200	[thread overview]
Message-ID: <20021001144536.A9408@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.GSO.4.44.0209270824140.8115-100000@helios.info-ua>; from barichar@info.univ-angers.fr on Fri, Sep 27, 2002 at 08:30:02AM +0200

> I wonder if anybody succeeded in making ocaml works with beos ?
> I have some trouble. The compilation step works fine, but some components
> (configure says shared dll not supported) are missing. So I can't compile
> my favorite little ocaml programs because of undefined function calls
> like "unix_getsockopt_bool". Of course it is says to be a unix function.

The patch below might help with this problem.

> I would like to know more about ocaml/beos. Is anybody has any experience
> about that ?

Well, I did the BeOS port of OCaml in 1999, for the versions of OCaml
and BeOS that were current at that time.  The native-code compiler
worked fine, but several libraries were missing (e.g. TK).

Since BeOS went belly up, I'm afraid there isn't much to say about
OCaml/BeOS except "rest in peace".

- Xavier Leroy

Index: csl/otherlibs/unix/sockopt.c
diff -c csl/otherlibs/unix/sockopt.c:1.17 csl/otherlibs/unix/sockopt.c:1.18
*** csl/otherlibs/unix/sockopt.c:1.17	Wed Jul 31 16:07:47 2002
--- csl/otherlibs/unix/sockopt.c	Tue Oct  1 14:34:58 2002
***************
*** 11,17 ****
  /*                                                                     */
  /***********************************************************************/
  
! /* $Id: sockopt.c,v 1.17 2002/07/31 14:07:47 xleroy Exp $ */
  
  #include <mlvalues.h>
  #include <alloc.h>
--- 11,17 ----
  /*                                                                     */
  /***********************************************************************/
  
! /* $Id: sockopt.c,v 1.18 2002/10/01 12:34:58 xleroy Exp $ */
  
  #include <mlvalues.h>
  #include <alloc.h>
***************
*** 209,218 ****
  
  #else
  
! CAMLprim value unix_getsockopt(value socket, value option)
  { invalid_argument("getsockopt not implemented"); }
  
! CAMLprim value unix_setsockopt(value socket, value option, value status)
  { invalid_argument("setsockopt not implemented"); }
  
  CAMLprim value unix_getsockopt_int(value socket, value option)
--- 209,218 ----
  
  #else
  
! CAMLprim value unix_getsockopt_bool(value socket, value option)
  { invalid_argument("getsockopt not implemented"); }
  
! CAMLprim value unix_setsockopt_bool(value socket, value option, value status)
  { invalid_argument("setsockopt not implemented"); }
  
  CAMLprim value unix_getsockopt_int(value socket, value option)
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      reply	other threads:[~2002-10-02  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27  6:30 Vincent Barichard
2002-10-01 12:45 ` Xavier Leroy [this message]

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=20021001144536.A9408@pauillac.inria.fr \
    --to=xleroy@pauillac.inria.fr \
    --cc=barichar@info.univ-angers.fr \
    --cc=caml-list@pauillac.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).