From: "Jhou ^^" <falajhou@gmail.com>
To: "Andres Varon" <avaron@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] OCamlMPI problem
Date: Tue, 25 Sep 2007 15:35:49 -0300 [thread overview]
Message-ID: <9efd48050709251135j2bb8bdffjfaf1dc5506dba8ef@mail.gmail.com> (raw)
In-Reply-To: <8BB4C643-AC23-44E8-A5AE-FF6888BB2D0E@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2485 bytes --]
Hi list!!!
After a hard work, I've eventually got testempi compiled. However, I'm
facing a new kind of problem now. When I just try to run testempi with
mpiexec tool, the 'mpd' process manager (that is, the default process
manager provided by MPICH2 implementation of MPI library) can not work
properly. Instead, I got an error message that says the 'lamd' daemon isn't
running. So, it asks me for starting 'lamboot'. So, I'm litte confused here:
is lamboot a tool from LAM/MPI Implementation, isn't it? Then, what about
MPICH2? I mean... do I need to use LAM/MPI to execute ocaml MPI application?
How can I get ocaml working good with MPICH2? 'cause I've already installed
and configured MPICH2 in my cluster.
By the way, does anybody know where to find a good tutorial about ocaml
MPI?? You know.. something with examples and so on!
Thanks in advance in sorry for my bad english!!
2007/9/18, Andres Varon <avaron@gmail.com>:
>
> You need to use mpicc as the C compiler and linker. That will take care of
> passing whatever flags are needed for proper compilation and linking. You
> can pass it to ocaml with:
> ocamlc -cc mpicc -o testmpi unix.cma mpi.cma test.ml -ccopt -L.
>
>
>
> Andres
>
>
> On Sep 17, 2007, at 5:08 PM, Rod wrote:
>
> Hi all,
>
> I'm trying to compile the test file using ocamlmpi, but just what I
> have is this message
>
> -------------------------------------------------------------------------------
> ocamlc -o testmpi unix.cma mpi.cma test.ml -ccopt -L.
> File "test.ml", line 144, characters 6-9:
> Warning Y: unused variable res.
> /usr/bin/ld: cannot find -lmpi
> collect2: ld returned 1 exit status
> Error while building custom runtime system
>
> -----------------------------------------------------------------------------
>
> I'm using mpich2-1.0.5p4.
>
> Thanks in advance for any answer.
>
> Cheer,
> Rodiney
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
[-- Attachment #2: Type: text/html, Size: 4534 bytes --]
prev parent reply other threads:[~2007-09-25 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 21:08 Rod
2007-09-17 21:45 ` [Caml-list] " skaller
2007-09-18 13:51 ` Andres Varon
2007-09-18 19:23 ` Rod
[not found] ` <AE44733D-5A0C-4176-B165-5EF7CDB9C0E7@gmail.com>
2007-10-07 21:33 ` Rod
2007-09-25 18:35 ` Jhou ^^ [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=9efd48050709251135j2bb8bdffjfaf1dc5506dba8ef@mail.gmail.com \
--to=falajhou@gmail.com \
--cc=avaron@gmail.com \
--cc=caml-list@yquem.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