From: jean-marc alliot <alliot@recherche.enac.fr>
To: Alain.Bengaouer@cea.fr
Cc: caml-list@inria.fr
Subject: Re: ocaml+pvm
Date: Fri, 23 Apr 1999 09:32:46 +0200 [thread overview]
Message-ID: <3720221E.C21B1A0@recherche.enac.fr> (raw)
In-Reply-To: <37200BA6.8B068D73@soleil.serma.cea.fr>
Alain Bengaouer wrote:
> We have a toplevel including ocaml2.02, and a C function calling
> pvm3.3.4, it appears that this toplevel,
> runs nicely on LINUX, AIX and SUN, but issues a segmentation violation
> on HPUX 10 when entering
> the pvm function.
> We have tried different compilers (GNU, or CC) and 2 versions of pvm
> (3.3.11 and 3.3.4).
> Has anyone had a similar problem ?
>
> Alain.Bengaouer@cea.fr
> CEA/DMT
Very strange. We have been using our own PVM/ML interface on many
different systems (including HPUX) and never had any problems.
Could you pass me your interface code along with the exact version of
HP-UX and HP C compiler you are using?
Jean-Marc
prev parent reply other threads:[~1999-04-23 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-23 5:56 ocaml+pvm Alain Bengaouer
1999-04-23 7:32 ` jean-marc alliot [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=3720221E.C21B1A0@recherche.enac.fr \
--to=alliot@recherche.enac.fr \
--cc=Alain.Bengaouer@cea.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