From: "Nicolas Pouillard" <nicolas.pouillard@inria.fr>
To: skaller <skaller@users.sourceforge.net>
Cc: nicolas.pouillard <nicolas.pouillard@gmail.com>,
caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] ocamlbuild
Date: Tue, 25 Sep 2007 13:45:18 +0200 [thread overview]
Message-ID: <1190720253-sup-6791@port-ext11.ensta.fr> (raw)
In-Reply-To: <1190046094.6058.26.camel@rosella.wigram>
Excerpts from skaller's message of Mon Sep 17 18:21:34 +0200 2007:
> On Mon, 2007-09-17 at 13:56 +0200, Nicolas Pouillard wrote:
> > Excerpts from skaller's message of Wed Sep 05 10:36:46 +0200 2007:
> > > hi .. I've got an ocamlbuild project which is hanging
> > > forever. Top shows 100% CPU and 2% memory. Any ideas how
> > > this could happen?
> > >
> > > I have a suspicion ocamlbuild can't handle directories
> > > properly..
> > >
> >
> > Are you on windows? If yes what kind of environment you have and what OCaml
> > you have.
> >
> > If it's Unix, have you symbolic links that make cycles (this case has been
> > handled, but I cannot see something else).
> >
> > Can you also try it with -no-sanitize.
Have you try this, since this part can be very time consuming.
> Our build system is portable, we need Ocamlbuild code to also be
> entirely portable. We know at present it doesn't work on Windows.
> But the problem is on Linux.
>
> Now, I have no idea what the problem was because I deleted the entire
> workspace and re-created it from the repository and it went away.
> We don't make any symbolic links because the script is portable,
> and you can't make them on Windows.
>
> So just keep an eye out for someone having a similar problem.
Is you source tree very big?
> Erick reports another issue: ocamlbuild tries to rebuild
> libraries a code depends on -- but not the system libraries.
Yes it even don't know that's system libraries.
> The idea of building a library is to *avoid* having to do
> any dependency checking on the module level. Is there some
> way to fix this? I.e, to 'make' a library, and then have
> it treated as a 'system' library.
Yes you can do it by showing it the directory with compiled files.
Then you have to explain it that all these .cmo,.cmi... are not junk files.
Example of using a library in /usr/lib/ocaml/foolib
$ ln -s /usr/lib/ocaml/foolib foolib
$ cat _tags
"foolib": include, precious
The first tag (include) is equivalent to a `-I foolib' given to ocamlbuild. The second tag (precious, also known as not_hygienic) tell him to don't report these files as junk and propose their deletion.
Regards,
--
Nicolas Pouillard aka Ertai
next prev parent reply other threads:[~2007-09-25 11:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 8:36 ocamlbuild skaller
2007-09-17 11:56 ` [Caml-list] ocamlbuild Nicolas Pouillard
2007-09-17 16:21 ` skaller
2007-09-25 11:45 ` Nicolas Pouillard [this message]
2007-09-25 14:19 ` skaller
2007-09-26 8:42 ` Nicolas Pouillard
-- strict thread matches above, loose matches on Subject: below --
2007-08-05 23:19 ocamlbuild skaller
2007-08-06 7:36 ` [Caml-list] ocamlbuild Adrien
2007-08-06 9:34 ` Adrien
2007-08-06 12:14 ` David Allsopp
2007-08-06 16:19 ` Christophe TROESTLER
2007-08-08 4:12 ` Aleksey Nogin
2007-08-09 18:35 ` Nicolas Pouillard
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=1190720253-sup-6791@port-ext11.ensta.fr \
--to=nicolas.pouillard@inria.fr \
--cc=caml-list@yquem.inria.fr \
--cc=nicolas.pouillard@gmail.com \
--cc=skaller@users.sourceforge.net \
/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