From: Brian Rogoff <bpr@best.com>
To: rakesh malhotra <rakesh@arches.uga.edu>
Cc: caml-list@inria.fr
Subject: [Caml-list] Re: your mail
Date: Wed, 7 Mar 2001 08:53:15 -0800 (PST) [thread overview]
Message-ID: <Pine.BSF.4.21.0103070845490.16796-100000@shell5.ba.best.com> (raw)
In-Reply-To: <Pine.A41.4.10.10103061523240.65164-100000@archa14.cc.uga.edu>
(Note: Please Pierre, come back, this list needs moderation!)
The answer is in the INSTALL file at the top level of the source
distribution.
INSTALLATION INSTRUCTIONS
1- Configure the system. From the top directory, do:
...
-tkdefs <cpp flags> (default: none)
-tklibs <flags and libraries> (default: determined automatically)
...
Find out where your Tcl stuff is installed and configure with the correct
options.
-- Brian
On Tue, 6 Mar 2001, rakesh malhotra wrote:
> hi:
> I get the following error when trying to install OCaml on a sun
> sparc station.
>
> Please help.
>
> thanks
>
> rakesh
>
>
> Options for linking with X11: -cclib -lX11
> NDBM found (in /usr/include)
> Configuring LablTk...
> tcl.h not found.
> Configuration failed, LablTk will not be built.
>
> ** Configuration summary **
>
> Directories where Objective Caml will be installed:
> binaries.................. /usr/local/bin
> standard library.......... /usr/local/lib/ocaml
> manual pages.............. /usr/local/man/man1 (with extension .1)
> Configuration for the bytecode compiler:
> C compiler used........... gcc
> options for compiling..... -fno-defer-pop -Wall -Wno-unused
> options for linking....... -lcurses -lnsl -lsocket -lm
> Configuration for the native-code compiler:
> hardware architecture..... sparc
> OS variant................ solaris
> C compiler used........... gcc
> options for compiling..... -Wall -Wno-unused
> options for linking....... -lcurses -lnsl -lsocket -lm
> assembler ................ $(AS)
> preprocessed assembler ... gcc -c -DSYS_$(SYSTEM)
> profiling with gprof ..... not supported
> Source-level replay debugger: supported
> Configuration for the external libraries:
> libraries supported ...... unix str num dynlink bigarray threads
> graph dbm
> The "num" library:
> target architecture ...... supersparc-solaris
> The "graph" library:
> options for compiling ....
> options for linking ...... -cclib -lX11
> The "labltk" library: configuration failed
> -------------------
> To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
>
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-03-07 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 20:25 rakesh malhotra
2001-03-07 16:53 ` Brian Rogoff [this message]
2001-08-03 10:58 Johann Spies
2001-08-03 13:26 ` [Caml-list] Re: your mail Francois Pottier
2001-08-03 17:42 ` Vitaly Lugovsky
2002-01-21 23:27 cgillot
2002-01-21 22:43 ` [Caml-list] Re: your mail Markus Mottl
2002-01-22 9:00 ` Daniel de Rauglaudre
2002-01-22 13:12 ` Markus Mottl
2003-02-07 5:23 Nikolaj Bjorner
2003-02-07 13:10 ` [Caml-list] Re: your mail Mike Potanin
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=Pine.BSF.4.21.0103070845490.16796-100000@shell5.ba.best.com \
--to=bpr@best.com \
--cc=caml-list@inria.fr \
--cc=rakesh@arches.uga.edu \
/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).