From: xclerc <xavier.clerc@inria.fr>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] PowerPC 405
Date: Mon, 30 Mar 2009 15:45:43 +0200 [thread overview]
Message-ID: <B75B1A35-E8CD-4A32-A566-D832982091E7@inria.fr> (raw)
In-Reply-To: <49CD0AB7.8000200@inria.fr>
Le 27 mars 09 à 18:19, Xavier Leroy a écrit :
> Just to complement Basile's excellent answers:
>
>> Do you know if it is possible to compile caml code on a PowerPC 405
>> from the Vertex 4 family ?
>> We'd like to put this processor in a FPGA. On the Caml's website,
>> it is written "PowerPC" but is it only for Macintosch ?
>
> Not just Macintosh: PowerPC/Linux is also supported and works very
> well.
>
>> Yes, it will run Linux. It will have the uclibC or even the lib C.
>
> Then you're in good shape. I would expect a basic OCaml system to
> work with uclibC, although a number of external libraries might not.
> With GNU libC, everything will work but watch out for code size:
> glibc is big!
>
>> The best case is to run native code for better performance. We'd
>> like to cross-compile for the PowerPC.
>
> Setting up OCaml as a cross-compiler is a bit of a challenge at the
> moment. As a prerequisite, you'll need a complete cross-compilation
> environment for C: cross-compiler, cross-binutils, libraries and
> header files for your target. It sounds obvious but in my experience
> that's quite hard to get right. Then, there is a bit of configuration
> magic to be done on the OCaml side. Write back for help if you're
> going to follow this way.
I have built a MacOS-to-Linux cross-compiler last week.
I do confirm that the hard part is getting a cross-[g]cc up and running.
In fact, this is so tedious that I strongly encourage to resort to
either
a prepackaged cross-[g]cc (from binaries, from a Linux packaging
system, whatever), or to the excellent "crosstool" available at :
http://www.kegel.com/crosstool/
On the OCaml side, there are very few things to do and they are
quite straightforward. First, you have to emulate the behaviour of
"./configure" by producing "config/m.h", "config/s.h", and "config/
Makefile"
by hand. This is easier than it may sound, just start from "config/m-
templ.h",
"config/s-temp.h", and "config/Makefile-templ" (these are
comprehensively
commented).
Then, you will have to slightly patch some Makefiles, and you are done.
I will setup a webpage with all the necessary steps and patches as soon
as I get my notes organized. This will allow us to share knowledge on
the subject.
Xavier Clerc
next prev parent reply other threads:[~2009-03-30 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 15:04 Gregory Bellier
2009-03-27 15:10 ` [Caml-list] " Basile STARYNKEVITCH
2009-03-27 15:56 ` Gregory Bellier
2009-03-27 16:05 ` Basile STARYNKEVITCH
2009-03-27 17:19 ` Xavier Leroy
2009-03-30 7:30 ` Gregory Bellier
2009-03-30 13:45 ` xclerc [this message]
2009-04-01 14:12 ` xclerc
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=B75B1A35-E8CD-4A32-A566-D832982091E7@inria.fr \
--to=xavier.clerc@inria.fr \
--cc=caml-list@yquem.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