caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Denis Bueno" <dbueno@gmail.com>
To: "Chris King" <colanderman@gmail.com>
Cc: "OCaml Mailing List" <caml-list@inria.fr>
Subject: Re: Re: [Caml-list] Odd OCAMLRUNPARAM behavior
Date: Sat, 16 Sep 2006 11:38:45 -0400	[thread overview]
Message-ID: <6dbd4d000609160838x41958ad3ha8426a4be0748a42@mail.gmail.com> (raw)
In-Reply-To: <875c7e070609160752x1f26617ai41166f3cd7c4d038@mail.gmail.com>

On 9/16/06, Chris King <colanderman@gmail.com> wrote:
> On 9/16/06, Denis Bueno <dbueno@gmail.com> wrote:
> > What could explain this behavior?
>
> Did you remember to "export OCAMLRUNPARAM"?

No.

Funny, I thought if you didn't export that the variable wouldn't even
show up in the shell. Thanks for the tip.

-Denis


      reply	other threads:[~2006-09-16 15:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-16 14:45 Denis Bueno
2006-09-16 14:52 ` [Caml-list] " Chris King
2006-09-16 15:38   ` Denis Bueno [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=6dbd4d000609160838x41958ad3ha8426a4be0748a42@mail.gmail.com \
    --to=dbueno@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=colanderman@gmail.com \
    /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).