caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Gerd Stolpmann" <info@gerd-stolpmann.de>
To: "Zhu Ping" <zhuping@comp.nus.edu.sg>
Cc: matthieu.dubuget@laposte.net, caml-list@yquem.inria.fr,
	"Anil Madhavapeddy" <anil@recoil.org>
Subject: Re: [Caml-list] Using Frontc
Date: Mon, 21 Nov 2005 10:54:56 +0100 (CET)	[thread overview]
Message-ID: <4373.192.168.1.2.1132566896.squirrel@gps.dynxs.de> (raw)
In-Reply-To: <000e01c5ee77$724858b0$1db312ac@comp.nus.edu.sg>

> The pity now is the CIL format seems too complicated for me. I like the
> data
> structure defined in an earlier version of FrontC
> (http://casse.hugues.free.fr/projects/frontc.html) better:). However I
> still
> have problems in compiling FrontC sources downloaded from the site
> http://casse.hugues.free.fr/projects/frontc.html. Did anyone successfully
> install FrontC in Linux/Unix?

FrontC is available in GODI, http://godi.ocaml-programming.de. This is
probably the simplest way to install it. Furthermore, this also simplifies
using libraries, as GODI supports findlib for all libraries, i.e. you just
say

ocamlfind ocamlc -package frontc -c your_module.ml

and get rid of the .cma nightmare.

Gerd

> ----- Original Message -----
> From: "Matthieu Dubuget" <matthieu.dubuget@laposte.net>
> To: "Zhu Ping" <zhuping@comp.nus.edu.sg>
> Cc: "Anil Madhavapeddy" <anil@recoil.org>; <caml-list@yquem.inria.fr>
> Sent: Sunday, November 20, 2005 8:37 PM
> Subject: Re: [Caml-list] Using Frontc
>
>
>>
>>> ocamlc -o main -I /home/sand/cil/obj/x86_LINUX/ pretty.cmo trace.cmo
>>> errormsg.cmo cabs.cmo cabsvisit.cmo escape.cmo cprint.cmo patch.cmo
>>> frontc.cmo main.cmo
>>> "Error while linking /home/sand/cil/obj/x86_LINUX/patch.cmo: Reference
>>> to undefined global 'Unix' "
>>
>> Try this :
>> ocamlc -o main -I /home/sand/cil/obj/x86_LINUX/ unix .cma pretty.cmo
>> trace.cmo errormsg.cmo cabs.cmo cabsvisit.cmo escape.cmo cprint.cmo
>> patch.cmo frontc.cmo main.cmo
>>
>> Salutations
>>
>> Matthieu
>>
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>


------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany
gerd@gerd-stolpmann.de          http://www.gerd-stolpmann.de
------------------------------------------------------------



  reply	other threads:[~2005-11-21  9:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20  8:44 Zhu Ping
2005-11-20 12:37 ` Matthieu Dubuget
2005-11-21  8:41   ` Zhu Ping
2005-11-21  9:54     ` Gerd Stolpmann [this message]
2005-11-24  6:12       ` Zhu Ping
2005-11-24 10:25         ` skaller
  -- strict thread matches above, loose matches on Subject: below --
2005-11-18  9:22 Zhu Ping
2005-11-18  9:52 ` [Caml-list] " Anil Madhavapeddy

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=4373.192.168.1.2.1132566896.squirrel@gps.dynxs.de \
    --to=info@gerd-stolpmann.de \
    --cc=anil@recoil.org \
    --cc=caml-list@yquem.inria.fr \
    --cc=matthieu.dubuget@laposte.net \
    --cc=zhuping@comp.nus.edu.sg \
    /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).