caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: r0ller <r0ller@freemail.hu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ocamlc compiles hello world, ocamlopt not
Date: Fri, 11 Jan 2013 10:56:44 +0100	[thread overview]
Message-ID: <50EFE1DC.9060907@inria.fr> (raw)
In-Reply-To: <freemail.20130111102825.32442.2@xmldata03.freemail.hu>

On 01/11/2013 10:28 AM, r0ller wrote:

> Minix3 is an ELF based system indeed. I asked the guys on the minix3 forum and one of the developers said that neither the default minix toolchain (clang) nor the minix port of gcc prepends leading underscores. However, he had a hint about checking if the ocaml package itself is trying to guess during its build whether leading underscore prepending is done on the host system or not.

Indeed, the "configure" script tries to guess this, among other
platform dependencies.

> If that's true, I'd need to recompile the ocaml package whilst trying to indicate somehow that the minix3 system does not need leading underscore prepending, right?

Yes.  For your first try, just manually edit the generated file
config/Makefile so that it has

ARCH=i386
MODEL=default
SYSTEM=linux_elf

then do "make opt" and "make opt.opt" and see if it now works.

If it does, you may want to investigate why the ./configure script
guessed wrong on your Minix system.  Running "sh -x ./configure"
generates a useful trace.

- Xavier Leroy

  reply	other threads:[~2013-01-11  9:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 14:48 r0ller
2013-01-10 16:08 ` Gerd Stolpmann
2013-01-11  9:28   ` r0ller
2013-01-11  9:56     ` Xavier Leroy [this message]
     [not found] <fa.rDSh+u4grOqB/jgTnZaDUQoT+s0@ifi.uio.no>
     [not found] ` <fa.53tG84D0PDsZ/dZaWLkOQvsLfTU@ifi.uio.no>
2013-01-16 10:20   ` r0ller
     [not found] <fa.tMEIU2eZ10ydMQJpEId8zYmuWpo@ifi.uio.no>
     [not found] ` <fa.5ytRg9PGwzfRT5U12a+96CThPHM@ifi.uio.no>
     [not found]   ` <fa.fEvQzwMsL9tn+Q+kKoqZrwKQpHs@ifi.uio.no>
     [not found]     ` <fa.gj9h88pWsiKoDqywSvikWobc2Gk@ifi.uio.no>
     [not found]       ` <fa.yuD604fWUWzMhQKQ2PVUY9+PSRs@ifi.uio.no>
     [not found]         ` <fa.SiWjqBgSRaJHHtRDr1LQlRGec/I@ifi.uio.no>
2013-01-16  9:29           ` r0ller
     [not found]           ` <fa.vGYTX053VB/7kO+WVlnBXs6LyWM@ifi.uio.no>
2013-01-16  9:36             ` r0ller
     [not found]             ` <fa.3ZA77VqUCTh0CDJf/dKc9fxM234@ifi.uio.no>
2013-01-16 10:16               ` r0ller
     [not found] <fa.J86NbZyp4NcoVDLx3IIZPjh6Xsw@ifi.uio.no>
     [not found] ` <fa.cI6IwITMmpEcG/xX8jnbm1tXnWU@ifi.uio.no>
2013-01-11 16:13   ` r0ller
2013-01-11 16:23     ` r0ller
2013-01-16  8:02       ` r0ller
2013-01-16  8:56         ` Francois Berenger
2013-01-16  9:01           ` AW: " Gerd Stolpmann
2013-01-16  9:48             ` Basile Starynkevitch
2013-01-16 22:32               ` Benedikt Meurer
2013-01-16 23:17                 ` Gabriel Scherer
2013-01-17 19:34                   ` Benedikt Meurer
  -- strict thread matches above, loose matches on Subject: below --
2013-01-10 13:57 r0ller
2013-01-10 14:25 ` Gerd Stolpmann

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=50EFE1DC.9060907@inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=r0ller@freemail.hu \
    /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).