caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Francois Berenger <berenger@riken.jp>
To: caml-list@inria.fr
Subject: Re: AW: [Caml-list] ocamlc compiles hello world, ocamlopt not
Date: Thu, 17 Jan 2013 10:10:58 +0900	[thread overview]
Message-ID: <50F74FA2.4070805@riken.jp> (raw)
In-Reply-To: <1358326866.28639.13@samsung>

On 01/16/2013 06:01 PM, Gerd Stolpmann wrote:
> Am 16.01.2013 09:56:55 schrieb(en) Francois Berenger:
>> On 01/16/2013 05:02 PM, r0ller@freemail.hu wrote:
>>> Hi All,
>>>
>>> By the way, is there any doc available about porting ocaml (google
>>> didn't find any) or any hint on how to move forward? I'd really like
>>> to have the native compiler on minix too.
>>
>> I think in the past it was possible to generate C code from OCaml code.
>
> There is no real C backend (and has never been). The only thing you can
> do is to embed bytecode in a C-friendly way (what -output-obj does). But
> it is still bytecode.

Sorry for the mistake.

I see in the rest of this thread that some current work on bytecode
to C generation is mentioned.
I may have mixed several things together.

Was this C code generation not possible even with Caml code
back in the era of Caml?

Regards,
F.

> Gerd
>
>> As I guess Minix have a C compiler, that would be a way out for you.
>>
>> I can't find back, but I remember Richard W.M. Jones from Red Hat
>> posted about it on caml-list and keeps it somewhere.
>>
>>> Thanks&regards,
>>> r0ller
>>>
>>> On Friday, January 11, 2013 5:23:54 PM UTC+1, r0l...@freemail.hu wrote:
>>>> Hi again,
>>>>
>>>>
>>>>
>>>> I forgot to mention that this result I got after gmake opt.
>>>>
>>>>
>>>>
>>>> Regards,
>>>>
>>>> r0ller
>>>>
>>>>
>>>>
>>>> On Friday, January 11, 2013 5:13:56 PM UTC+1, r0l...@freemail.hu wrote:
>>>>
>>>>> 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
>>>
>>>
>>
>>
>> --
>> 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
>>
>
>


  parent reply	other threads:[~2013-01-17  1:11 UTC|newest]

Thread overview: 13+ 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
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             ` Francois Berenger [this message]
2013-01-17  7:53               ` AW: " Alain Frisch
2013-01-16  9:36 r0ller
2013-01-16  9:53 ` AW: " Gerd Stolpmann
     [not found] <fa.yuD604fWUWzMhQKQ2PVUY9+PSRs@ifi.uio.no>
     [not found] ` <fa.SiWjqBgSRaJHHtRDr1LQlRGec/I@ifi.uio.no>
     [not found]   ` <fa.vGYTX053VB/7kO+WVlnBXs6LyWM@ifi.uio.no>
     [not found]     ` <fa.AgEvtE0xHcqZGBKj0Yv0NqpqfDI@ifi.uio.no>
     [not found]       ` <fa.U9QIrhkTeSswG97/yP/PR0sEGRA@ifi.uio.no>
2013-01-17 13:06         ` r0ller

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=50F74FA2.4070805@riken.jp \
    --to=berenger@riken.jp \
    --cc=caml-list@inria.fr \
    /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).