caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Rhythmic Fistman" <rfistman@gmail.com>
To: skaller <skaller@users.sourceforge.net>
Cc: felix-impl <felix-impl@lists.sourceforge.net>,
	"Emmanuel Onzon" <emmanuel.onzon@ens-lyon.fr>,
	caml-list <caml-list@inria.fr>
Subject: Re: [Felix-impl] it no me build
Date: Tue, 15 May 2007 22:27:59 +0200	[thread overview]
Message-ID: <131e28b50705151327h6f99aceerec01e9d3a10e883f@mail.gmail.com> (raw)
In-Reply-To: <1179258190.7592.46.camel@rosella.wigram>

On 5/15/07, skaller <skaller@users.sourceforge.net> wrote:
> On Tue, 2007-05-15 at 21:00 +0200, Rhythmic Fistman wrote:
>
> > > The Felix build scripts ARE different .. but the effect should
> > > be the same. Any which way it should either fail on all platforms
> > > or build on all platforms .. there's no C code here, and Ocaml
> > > is supposed to be portable.
> >
> > Somewhere... someone lied.
> >
> > Haha, just kidding. The difference is that the tarball uses ocamlc and
> > flx here is using ocamlc.opt. Could that be relevant?
>
> As I understand it:
>
> No. ocamlc.opt and ocamlc are functionally equivalent.
> The only difference is ocamlc is compiled with ocamlc,
> whereas ocamlc.opt is compiled with ocamlopt.
>
> In other words, ocamlc.opt is faster because it is
> built as native code, but they're built from the
> same ocaml sources. Bootstrapping is cool!
>
> In fact there ARE differences between ocamlc
> and ocamlopt built code, apart from speed:
> for example bytecode supports dynamic loading
> of bytecode whereas native code does not ..
> but this shouldn't affect ocamlc.
>
> However, -pack MAY be different; it is a new feature
> and didn't work on any processor other than x86 originally,
> so this might be a difference. -pack does nasty stuff
> with native code which requires arcane knowledge of
> object files, whereas with bytecode it's the same on
> all platforms.

Can we disable -pack?
Can I fall back to ocamlc? How?


  reply	other threads:[~2007-05-15 20:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <131e28b50705141643l195bae7cxb80c278e5eec7c4f@mail.gmail.com>
2007-05-15  4:00 ` skaller
2007-05-15  4:29   ` [Caml-list] " Erick Tryzelaar
2007-05-15  8:48     ` Rhythmic Fistman
2007-05-15  9:06       ` [Felix-impl] [Caml-list] " skaller
2007-05-15  9:12         ` Rhythmic Fistman
2007-05-15  9:33           ` Erick Tryzelaar
2007-05-15  9:13         ` Rhythmic Fistman
2007-05-15  9:17           ` skaller
2007-05-15  9:33             ` Rhythmic Fistman
2007-05-15 17:47 ` [Felix-impl] " skaller
2007-05-15 19:00   ` Rhythmic Fistman
2007-05-15 19:43     ` skaller
2007-05-15 20:27       ` Rhythmic Fistman [this message]
2007-05-15 21:30         ` [Caml-list] " Erick Tryzelaar
2007-05-15 21:39           ` Emmanuel Onzon
2007-05-15 21:56             ` Erick Tryzelaar
     [not found]               ` <1179267261.7592.86.camel@rosella.wigram>
     [not found]                 ` <464A5F02.8030001@users.sourceforge.net>
2007-05-16  4:19                   ` [Felix-impl] [Caml-list] " skaller
2007-05-16  4:24                     ` Erick Tryzelaar

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=131e28b50705151327h6f99aceerec01e9d3a10e883f@mail.gmail.com \
    --to=rfistman@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=emmanuel.onzon@ens-lyon.fr \
    --cc=felix-impl@lists.sourceforge.net \
    --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;
as well as URLs for NNTP newsgroup(s).