caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Aaron Bohannon <bohannon@cis.upenn.edu>
To: Alexandre Pilkiewicz <alexandre.pilkiewicz@polytechnique.org>
Cc: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] specific ocaml software dependency question
Date: Fri, 1 Oct 2010 15:38:59 -0400	[thread overview]
Message-ID: <AANLkTi=To+wh5Nird3kbt7erP9487H31=GtWdnFBmo+H@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimY3eMJB+DiD80R3AN4b9YUrhHnfE5F38nJQ4Vx@mail.gmail.com>

Thanks Alexandre!

Well, it appears that, either due to openSUSE or our sys-admins,
camlp4 is actually *not* part of the installation of OCaml 3.11 on our
workstations.

The need for GODI has always baffled me.  There's plenty of OCaml
software available in good system-wide package managers (e.g.,
macports, which I use on OS X), and, at the same time, there are
always going to be *some* packages or software versions that are not
in GODI and so I'll have to end up manually installing those anyway.
If I use GODI too, then there would be at least three different places
my OCaml software might be living, at which point I start getting
confused.

That being said, the OCaml packages on my office machine are
sufficiently screwed up that starting from scratch with GODI may be my
best option in this case.

 - Aaron

On Fri, Oct 1, 2010 at 3:06 PM, Alexandre Pilkiewicz
<alexandre.pilkiewicz@polytechnique.org> wrote:
> Hi Aaron!
>
> If you have ocaml, you should have camlp4 since it's part of the
> standard distribution.
>
> For all "manual" installation of common ocaml programs, you should
> really look in the direction of godi (http://godi.camlcity.org). You
> should be able to install lablgtk2 from here without big difficulties.
>
> Good luck anyways
>
> Alexandre
>
> 2010/10/1 Aaron Bohannon <bohannon@cis.upenn.edu>:
>> Hi, I want to install Coq 8.3 + CoqIDE on my office's openSUSE Linux
>> machine (to which I do not have root access).  It depends on camlp5,
>> which was no problem for me to install in my home directory.  It also
>> depends on lablgtk2, which our sys-admins have installed on our
>> machines, but they or openSUSE must have screwed it up because
>> "dlllablgtk2.so" is nowhere to be found (I've looked), and this causes
>> my Coq compilation to fail.  I grudgingly decided to try to compile
>> and install lablgtk2 myself in my home directory, but its "configure"
>> script fails with the error "Cannot find camlp4o."  So I guess I need
>> to find camlp4 now, but Google has been of no help -- when you search
>> for camlp4, you only get pages talking about camlp5 (which, of course,
>> used to be called camlp4).  This is seeming WAY harder than it should
>> be.  Can anybody help?
>>
>>  - Aaron
>>
>> _______________________________________________
>> 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
>>
>


      reply	other threads:[~2010-10-01 19:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 18:52 Aaron Bohannon
2010-10-01 19:06 ` [Caml-list] " Alexandre Pilkiewicz
2010-10-01 19:38   ` Aaron Bohannon [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='AANLkTi=To+wh5Nird3kbt7erP9487H31=GtWdnFBmo+H@mail.gmail.com' \
    --to=bohannon@cis.upenn.edu \
    --cc=alexandre.pilkiewicz@polytechnique.org \
    --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).