caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: r0ller@freemail.hu
To: fa.caml@googlegroups.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ocamlc compiles hello world, ocamlopt not
Date: Fri, 11 Jan 2013 08:13:56 -0800 (PST)	[thread overview]
Message-ID: <7040befa-a99d-4fc7-86ff-9b70ea2174ef@googlegroups.com> (raw)
In-Reply-To: <fa.cI6IwITMmpEcG/xX8jnbm1tXnWU@ifi.uio.no>

Hi Xavier,

Thanks for the hint! I gave it a try and also with SYSTEM=bsd_elf. Please, find below the result of the latter (it's the same for linux_elf anyway). I also tried another suggestion from Olivier Andrieu by introducing SYS_minix in asmrun/i386.S but ended up in the same result:( Do you happen to know how to proceed now?

gmake runtimeopt
gmake[1]: Entering directory `/home/r0ller/ocaml-4.00.1'
cd asmrun; gmake all
gmake[2]: Entering directory `/home/r0ller/ocaml-4.00.1/asmrun'
DSYS_bsd_elf -o i386.o i386.S || \
{ echo "If your assembler produced syntax errors, it is probably unhappy with the"; echo "preprocessor. Check your assembler, or try producing i386.o by hand."; exit 2; }
DSYS_bsd_elf: not found
If your assembler produced syntax errors, it is probably unhappy with the
preprocessor. Check your assembler, or try producing i386.o by hand.
gmake[2]: [i386.o] Error 2 (ignored)
rm -f libasmrun.a
ar rc libasmrun.a startup.o main.o fail.o roots.o globroots.o signals.o signals_asm.o misc.o freelist.o major_gc.o minor_gc.o memory.o alloc.o compare.o ints.o floats.o str.o array.o io.o extern.o intern.o hash.o sys.o parsing.o gc_ctrl.o terminfo.o md5.o obj.o lexing.o printexc.o callback.o weak.o compact.o finalise.o custom.o unix.o backtrace.o natdynlink.o debugger.o meta.o dynlink.o i386.o
ar: i386.o: no such file or directory
gmake[2]: *** [libasmrun.a] Error 1
gmake[2]: Leaving directory `/home/r0ller/ocaml-4.00.1/asmrun'
gmake[1]: *** [makeruntimeopt] Error 2
gmake[1]: Leaving directory `/home/r0ller/ocaml-4.00.1'
gmake: *** [opt] Error 2

Thanks & regards,
r0ller

On Friday, January 11, 2013 10:56:51 AM UTC+1, Xavier Leroy wrote:
> 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
> 
> 
> 
> -- 
> 
> Caml-list mailing list.  Subscription management and archives:
> 
> https://sympa.inria.fr/sympa/arc/caml-list
> 
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> 
> Bug reports: http://caml.inria.fr/bin/caml-bugs


       reply	other threads:[~2013-01-11 16:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.J86NbZyp4NcoVDLx3IIZPjh6Xsw@ifi.uio.no>
     [not found] ` <fa.cI6IwITMmpEcG/xX8jnbm1tXnWU@ifi.uio.no>
2013-01-11 16:13   ` r0ller [this message]
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
2013-01-17  1:10             ` AW: " Francois Berenger
2013-01-17  7:53               ` Alain Frisch
     [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
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
  -- 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=7040befa-a99d-4fc7-86ff-9b70ea2174ef@googlegroups.com \
    --to=r0ller@freemail.hu \
    --cc=caml-list@inria.fr \
    --cc=fa.caml@googlegroups.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).