caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "David Allsopp" <dra-news@metastack.com>
To: "'OCaml List'" <caml-list@yquem.inria.fr>
Subject: RE: [Caml-list] OCaml on Maemo
Date: Thu, 25 Feb 2010 18:34:23 -0000	[thread overview]
Message-ID: <001101cab649$273c6de0$75b549a0$@romulus.metastack.com> (raw)
In-Reply-To: <f93a6bcc1002241045l550d005bt46ded447745e169b@mail.gmail.com>

Sebastian Mondet wrote:
> On my N810, thanks to the "easy debian" technique:
> http://wiki.maemo.org/Easy_Debian
>
> I got access to all the ocaml packages which are available on debian-ARM.
Everything I tried
> worked perfectly (but I only tried "text mode" apps).

That seemed a little heavy for the first day of having it but I've
bookmarked the link for the future!

Gerd Stolpmann wrote:
> Yes, I've tried similar years ago on the N800 (Maemo 4, however). I ran
into this problem at
> that time: http://caml.inria.fr/mantis/view.php?id=3746. The ARM code
generator was changed
> since then (will be released in Ocaml 3.12). Haven't tried that yet,
though.
>
> So far I remember the byte code compiler was no problem at all. Only the
native-code compiler had > these problems with FP instructions.

I had the same experience with 3.11.2 - the error message from configure
could be better, but that won't matter once it's fixed in 3.12.0 (as you
say).

Martin DeMello wrote:
> On Wed, Feb 24, 2010 at 9:44 PM, David Allsopp <dra-news@metastack.com>
wrote:
> > My shiny new Nokia N900 has finally arrived so, of course, having got
> > bash, vim and texlive successfully installed I naturally need a
> > compiler!
> >
> > Before I dig into trying to compile OCaml on Maemo 5, can I ask if
> > anyone else out there has already tried (and hopefully succeeded)?
> 
> No, I've mostly been playing with Vala since I got mine, but I'd love to
> hear how you manage with it. It's definitely on my to-do list.

Enabling the SDK repository allowed me to install bash, make, gcc,
libc6-dev, tcl8.5-dev, tk8.5-dev and libx11-dev.

(aside, which probably demonstrates my ignorance more than a bug/problem in
anything: I've never used aptitude before - I was amused that installing gcc
doesn't automatically upgrade glibc to the dev version as you end up with a
C compiler which can't link. Couldn't quite imagine a situation where that's
handy but hey ho!)

OCaml 3.12.0+dev17 compiles out of the box (using -prefix /opt/maemo) -
ocamlbrowser works (i.e. labltk) and ocamlopt is fine. The reference run of
a command line app of mine takes 5 mins 20 sec (impressive as it takes 31
seconds on my Intel P8600 laptop and used to take about 4:30 on the machine
on which it was originally developed). 


David


      reply	other threads:[~2010-02-25 18:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 16:14 David Allsopp
2010-02-24 16:35 ` [Caml-list] " Sebastien Mondet
2010-02-24 21:05   ` Sebastien Mondet
2010-02-25  8:45   ` Sebastien Ferre
2010-02-25  9:40     ` Sebastien Mondet
2010-02-24 16:54 ` Gerd Stolpmann
2010-02-24 18:45 ` Martin DeMello
2010-02-25 18:34   ` David Allsopp [this message]

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='001101cab649$273c6de0$75b549a0$@romulus.metastack.com' \
    --to=dra-news@metastack.com \
    --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;
as well as URLs for NNTP newsgroup(s).