[Caml-list] Compiler ActiveDVI (CVS)

[Caml-list] Compiler ActiveDVI (CVS)

[David Marsal]

Bonjour,

Je me suis promis de faire ma prochaine presentation avec Advi.(dans 3 
semaines). Je suis sous Debian Sid.

Voulant profiter des derniers ajouts (image de fond) j'ai pris la 
version CVS et ... malheurs.

Je ne connait rien à ocaml pour l'instant. et voici le résultat de 
./configure

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

creating cache ./config.cache
checking your compiler package... version 3.04 at /usr/lib/ocaml
checking for cdk_config... nope
checking for kpsexpand... /usr/bin/kpsexpand
checking TeX root path... /usr/share/texmf
checking for kpsewhich... /usr/bin/kpsewhich
checking for gzip... /bin/gzip
checking for camlimages... found
checking for camltk... no
checking for gs... checking for gs... /usr/bin/gs
found
checking how to run the C preprocessor... gcc -E
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for dnet_ntoa in -ldnet... no
checking for dnet_ntoa in -ldnet_stub... no
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
updating cache ./config.cache
creating ./config.status
creating Makefile.config
creating config.ml
creating ifdef.ml
------------------------------------------------- Configuration finished
Language:    ocaml version 3.04
cdk_config:  false
Camlimages:  true
CamlTk:      false
GS:           version 6.51 at /usr/bin/gs
Resources:   /usr/local/lib/advi /
------------------------------------------------------------------------


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Comme il va au bout je suis content malgré quelques doutes avec 
cdk_config et CamlTk

Alors makons !

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Makefile:171: .depend: No such file or directory
ocamlc -g -c -I +camlp4 ifdef.ml
camlp4o pa_ifdef.cmo ./ifdef.cmo -impl drawimage.mlp > drawimage.ml
camlp4o pa_ifdef.cmo ./ifdef.cmo -impl dvicolor.mlp > dvicolor.ml
camlp4o pa_ifdef.cmo ./ifdef.cmo -impl ttfont.mlp > ttfont.ml
ocamldep *.mli config.ml timeout.ml graphicsY11.ml misc.ml userfile.ml 
input.ml symbol.ml search.ml shot.ml drawimage.ml dvicolor.ml table.ml 
pkfont.ml ttfont.ml jfm.ml font.ml glyph.ml devfont.ml units.ml 
dimension.ml gs.ml transimpl.ml grdev.ml dvi.ml driver.ml dviview.ml 
main.ml > .depend
gcc -MM -I/usr/lib/ocaml/caml -I/usr/X11R6/include -O -fno-defer-pop 
-Wall -Wno-unused events.c grY11.c | sed -e 's| /usr/lib/ocaml/caml/[^ 
]*||' >> .depend
In file included from events.c:16:
libgraph.h:19: warning: No include path in which to find mlvalues.h
events.c:17: warning: No include path in which to find alloc.h
grY11.c:17: warning: No include path in which to find alloc.h
grY11.c:20: warning: No include path in which to find fail.h
In file included from grY11.c:21:
libgraph.h:19: warning: No include path in which to find mlvalues.h
ocamlc -g -ccopt "-I/usr/lib/ocaml/caml -I/usr/X11R6/include -O 
-fno-defer-pop -Wall -Wno-unused" -c events.c
In file included from events.c:16:
libgraph.h:19: mlvalues.h: No such file or directory
events.c:17: alloc.h: No such file or directory
make: *** [events.o] Error 2

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

j'ai alors bidouillé pour faire des liens symboliques de /usr/lib/ocaml 
vers /usr/include/caml
ainsi la compilation va un peu plus loin puis me plante sur un -ltiff 
blablabla (un peu comme les erreurs avec -lX11)
J'ai également modif de /etc/ld.so.conf puis ldconfig et pis le truc ne 
marche pas ...  j'ai laissé tombé.

Vous l'avez compris je ne sais pas ce qu'il faut faire.
Alors je sollicite votre aide abondante et généreuse.
Par avance, un grand merci et une très bonne journée.

Pour note, voila les paquets caml installé

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

camlidl                                         install
camlidl-doc                                     install
camlimages                                      install
camlp4-doc                                      install
ocaml                                           install
ocaml-base                                      install
ocaml-core                                      install
ocaml-doc                                       install
ocaml-findlib                                   install
ocaml-tools                                     install
ocamlweb                                        install






-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Sven]

On Fri, Jan 25, 2002 at 08:23:25AM +0100, David Marsal wrote:
> Bonjour,
> 
> Je me suis promis de faire ma prochaine presentation avec Advi.(dans 3 
> semaines). Je suis sous Debian Sid.

Mmm, ...

1) il existe un package debian de mldvi, mais qui n'inclut peut-etre pas
toutes les nouveautes de Advi. Il faudrait que je package Advi, ou que je
remplace mldvi par ActiveDvi. Je ne sais pas ce qu'il en est exactement.

2) j'aimerait savroi quelle version des packages camlimages et ocaml tu
utilise, la derniere version de ocaml est 3.04-5 et la derniere version de
camlimages est 2.00-1.

> Voulant profiter des derniers ajouts (image de fond) j'ai pris la 
> version CVS et ... malheurs.
> 
> Je ne connait rien à ocaml pour l'instant. et voici le résultat de 
> ./configure
> 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
> creating cache ./config.cache
> checking your compiler package... version 3.04 at /usr/lib/ocaml
> checking for cdk_config... nope
> checking for kpsexpand... /usr/bin/kpsexpand
> checking TeX root path... /usr/share/texmf
> checking for kpsewhich... /usr/bin/kpsewhich
> checking for gzip... /bin/gzip
> checking for camlimages... found
> checking for camltk... no
> checking for gs... checking for gs... /usr/bin/gs
> found
> checking how to run the C preprocessor... gcc -E
> checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
> checking for dnet_ntoa in -ldnet... no
> checking for dnet_ntoa in -ldnet_stub... no
> checking for gethostbyname... yes
> checking for connect... yes
> checking for remove... yes
> checking for shmat... yes
> checking for IceConnectionNumber in -lICE... yes
> updating cache ./config.cache
> creating ./config.status
> creating Makefile.config
> creating config.ml
> creating ifdef.ml
> ------------------------------------------------- Configuration finished
> Language:    ocaml version 3.04
> cdk_config:  false
> Camlimages:  true
> CamlTk:      false
> GS:           version 6.51 at /usr/bin/gs
> Resources:   /usr/local/lib/advi /
> ------------------------------------------------------------------------
> 
> 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
> Comme il va au bout je suis content malgré quelques doutes avec 
> cdk_config et CamlTk
> 
> Alors makons !
> 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
> Makefile:171: .depend: No such file or directory
> ocamlc -g -c -I +camlp4 ifdef.ml
> camlp4o pa_ifdef.cmo ./ifdef.cmo -impl drawimage.mlp > drawimage.ml
> camlp4o pa_ifdef.cmo ./ifdef.cmo -impl dvicolor.mlp > dvicolor.ml
> camlp4o pa_ifdef.cmo ./ifdef.cmo -impl ttfont.mlp > ttfont.ml
> ocamldep *.mli config.ml timeout.ml graphicsY11.ml misc.ml userfile.ml 
> input.ml symbol.ml search.ml shot.ml drawimage.ml dvicolor.ml table.ml 
> pkfont.ml ttfont.ml jfm.ml font.ml glyph.ml devfont.ml units.ml 
> dimension.ml gs.ml transimpl.ml grdev.ml dvi.ml driver.ml dviview.ml 
> main.ml > .depend
> gcc -MM -I/usr/lib/ocaml/caml -I/usr/X11R6/include -O -fno-defer-pop 
> -Wall -Wno-unused events.c grY11.c | sed -e 's| /usr/lib/ocaml/caml/[^ 
> ]*||' >> .depend
> In file included from events.c:16:
> libgraph.h:19: warning: No include path in which to find mlvalues.h
> events.c:17: warning: No include path in which to find alloc.h
> grY11.c:17: warning: No include path in which to find alloc.h
> grY11.c:20: warning: No include path in which to find fail.h
> In file included from grY11.c:21:
> libgraph.h:19: warning: No include path in which to find mlvalues.h
> ocamlc -g -ccopt "-I/usr/lib/ocaml/caml -I/usr/X11R6/include -O 
> -fno-defer-pop -Wall -Wno-unused" -c events.c
> In file included from events.c:16:
> libgraph.h:19: mlvalues.h: No such file or directory
> events.c:17: alloc.h: No such file or directory
> make: *** [events.o] Error 2
> 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
> j'ai alors bidouillé pour faire des liens symboliques de /usr/lib/ocaml 
> vers /usr/include/caml

Arg, ...

/usr/include/caml est l'emplacement correct pour les fichier d'include caml,
comme il se doit. C'est une idee bizarre de mettre des fichiers d'include dans
/usr/lib, bien que je comprenne pourquoi ocaml fait cela, pour le package
debian on a la chance de pouvoir placer les fichier au bon endroit.

L'ideal aurrait ete de pouvoir changer les chemins des includes dans le
configure ou le makefile de Advi.

> ainsi la compilation va un peu plus loin puis me plante sur un -ltiff 
> blablabla (un peu comme les erreurs avec -lX11)

est-ce que tu a installer une librairie tiff ? camlimages ne smeble pas
dependre de tels librairies, mais stefano vient juste d'en faire un package,
et ce serait peut etre un bug de son package.

> J'ai également modif de /etc/ld.so.conf puis ldconfig et pis le truc ne 
> marche pas ...  j'ai laissé tombé.

Ok, ... Je vais donc de ce pas faire un package debian de Advi (derniere
release officiel, pas cvs).

> Vous l'avez compris je ne sais pas ce qu'il faut faire.
> Alors je sollicite votre aide abondante et généreuse.
> Par avance, un grand merci et une très bonne journée.
> 
> Pour note, voila les paquets caml installé

une sortie de dpkg -l \*caml\* aurrait ete plus instructive, en particulier
pour les versions installe.

Ceci dis, la bonne maniere de resoudre ce genre de probleme, est de faire un
rapport de bug contre le package debian incriminer (ocaml ou cmalimages) ou
eventuellement d'envoyer un mail a debian-ocaml-maint@lists.debian.org.

> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
> camlidl                                         install
> camlidl-doc                                     install
> camlimages                                      install
> camlp4-doc                                      install
> ocaml                                           install
> ocaml-base                                      install
> ocaml-core                                      install
> ocaml-doc                                       install
> ocaml-findlib                                   install
> ocaml-tools                                     install
> ocamlweb                                        install

Amicalement,

Sven Luther
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Jun P.FURUSE]

Bonjour,

> /usr/include/caml est l'emplacement correct pour les fichier d'include caml,
> comme il se doit. C'est une idee bizarre de mettre des fichiers d'include dans
> /usr/lib, bien que je comprenne pourquoi ocaml fait cela, pour le package
> debian on a la chance de pouvoir placer les fichier au bon endroit.
> 
> L'ideal aurrait ete de pouvoir changer les chemins des includes dans le
> configure ou le makefile de Advi.

Since I know nothing about the directory layout of O'Caml system in Debian,
I am not sure what is happening...

But I fixed the CFLAGS setting of Advi Makefile so that now ocamlc can use
its default cc include path (usually -I /usr/local/lib/ocaml) correctly.
I hope this may help you...

# The next release of Advi is soon...

--
Jun
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Sven]

On Fri, Jan 25, 2002 at 02:56:51PM +0100, Jun P.FURUSE wrote:
> Bonjour,
> 
> > /usr/include/caml est l'emplacement correct pour les fichier d'include caml,
> > comme il se doit. C'est une idee bizarre de mettre des fichiers d'include dans
> > /usr/lib, bien que je comprenne pourquoi ocaml fait cela, pour le package
> > debian on a la chance de pouvoir placer les fichier au bon endroit.
> > 
> > L'ideal aurrait ete de pouvoir changer les chemins des includes dans le
> > configure ou le makefile de Advi.
> 
> Since I know nothing about the directory layout of O'Caml system in Debian,
> I am not sure what is happening...

Well, basically, everything is in /usr/lib/ocaml as usual, only i moved the
includes in the more logical /usr/include/caml directory. Which may be one of
the reason of this causing problems. That said, i built activeDVI 0.3.1
without any kind of major problems.

> But I fixed the CFLAGS setting of Advi Makefile so that now ocamlc can use
> its default cc include path (usually -I /usr/local/lib/ocaml) correctly.
> I hope this may help you...

I guess so, will try it out later on.

> # The next release of Advi is soon...

Cool, ...

BTW, i currently ship both mldvi and activedvi as debian package, mldvi being
1.0 and activedvi being 0.3.1. I think this may be overkill, but since i am
not entirely sure of what you or alexandre have thinked about it, i prefer to
keep it as such (and well, going from 1.0 to 0.3.1 version is not nice for
debian packages, i could manage it, but would prefer not to). 

Also, i have written a small manpage for mldvi (which i send to alexandre i
think) and upgraded it for activedvi. You may want to look at it, change
things as needed, and integrate it into the cvs archive. (attached here).

Also, may you consider adding some small changes to the makefile i need in
order to make debianization of it easier ? It is only the following :

--- activedvi-0.3.1.orig/Makefile
+++ activedvi-0.3.1/Makefile
@@ -88,6 +88,15 @@
 .depend: *.mli *.ml
        $(OCAMLDEP) $(INCLUDES) *.mli *.ml > .depend
 
+# debian matters
+#
+install: mldvi
+       install mldvi $(DESTDIR)/usr/bin
+       install mldvi.1 $(DESTDIR)/usr/share/man/man1
+install.opt: mldvi.opt
+       install mldvi.opt $(DESTDIR)/usr/bin
+       install mldvi.opt.1 $(DESTDIR)/usr/share/man/man1
+
 # just for the authors
 WEBSITEDIR=/net/pauillac/infosystems/www/activedvi
 
As you see, i need a install target, which i can modify the directory prefix
with something akin to this $(DESTDIR) variable.

Also we could imagine moving all the debian subdir into cvs, so people could
build packages directly out of cvs, ...

(I still didn't had time to work on the lablgtk frontend to ml/activedvi
wanted to do:((()

Friendly,

Sven Luther
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Sven]

[-- Attachment #1: Type: text/plain, Size: 353 bytes --]

On Fri, Jan 25, 2002 at 03:07:04PM +0100, Sven wrote:
> 
> Also, i have written a small manpage for mldvi (which i send to alexandre i
> think) and upgraded it for activedvi. You may want to look at it, change
> things as needed, and integrate it into the cvs archive. (attached here).
> 

Sorry, forgot to attach the man pages.

Friendly,

Sven Luther

[-- Attachment #2: mldvi.1 --]
[-- Type: text/plain, Size: 5377 bytes --]

.\"                                      Hey, EMACS: -*- nroff -*-
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH MLDVI SECTION "mars 23, 2000"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
.\" .nh        disable hyphenation
.\" .hy        enable hyphenation
.\" .ad l      left justify
.\" .ad b      justify to both left and right margins
.\" .nf        disable filling
.\" .fi        enable filling
.\" .br        insert line break
.\" .sp <n>    insert n+1 empty lines
.\" for manpage-specific macros, see man(7)
.SH NAME
mldvi \- a simple DVI previewer written in Objective Caml.
.UR http://caml.inria.fr/ocaml/
(http://caml.inria.fr/ocaml/)
.UE
.SH VERSION
ActiveDVI 0.3.1 (based on mldvi 1.0)
.SH SYNOPSIS
.B mldvi
.RI [ options ] " dvifile" ...

.B mldvi.opt
.RI [ options ] " dvifile" ...
.SH DESCRIPTION
This manual page documents briefly the
.B mldvi and native code 
.B mldvi.opt
commands.

This manual page was written for the Debian GNU/Linux distribution
because the original program does not have a manual page.

.SH CURRENTLY SUPPORTED FEATURES:

\- Antialiasing

\- Color (as defined in the LaTeX package `color')

\- Automatic recompilation of METAFONT fonts

\- Automatic reloading of the file after modification

+ Encapsulated Postscript File inclusion (using graphics package)

+ Some effects for presentation (pause, delay, text color change)

Notice that mldvi needs the `kpsewhich' tool in order to find and
recompile PK fonts.  (This program is part of the `kpathsea' library
provided by many TeX distributions.)

.SH OPTIONS
Options are : 

.TP
.B \-g GEOM, \-geometry GEOM
sets the (maximum) geometry GEOM
.TP
.B \-crop
crop the window to the best size (default)
.TP
.B \-no-crop
disable cropping
.TP
.B \-hmargin DIMEN
horizontal margin  (default: 1cm)
.TP
.B \-vmargin DIMEN
vertical margin    (default: 1cm)

.P
Geometry GEOM is specified in pixels, using the standard format
for specifying geometries (i.e: "WIDTHxHEIGHT[+XOFFSET+YOFFSET]").

Dimensions (for options `-hmargin' and `-vmargin') are specified as
numbers optionaly followed by two letters representing units.

When no units are given, dimensions are treated as numbers of pixels.

Currently supported units are the standard TeX units as specified in
the TeXbook (D. Knuth, Addison-Wesley, (C) 1986):

.RS 2
`pt' (point), `pc' (pica), `in' (inch), `bp' (big point),
`cm' (centimeter), `mm' (millimeter), `dd' (didot point),
`cc' (cicero) and `sp' (scaled point).
.RE
      
Notice that dimensions are specified w.r.t the original TeX document,
and do not correspond to what is actually shown on the screen, which
can be displayed at a different resolution than specified in the
original TeX source.

.SH KEYSTROKES

Mldvi recognizes the following keystrokes when typed in its window.
Each may optionally be preceded by a number, whose interpretation will
depend on the particular keystroke.

.RS 2
.TP 7 
.B q
Quits the program

.TP
.B n
Moves to the next page (or to the n-th next page if a number is given)

.TP
.B <space>
Moves to the next "pause" in the current page

.TP
.B p
Moves to the previous page (or back n pages).

.TP
.B g
Moves to the page with the given number.  The first page is numbered 1.

.TP
.B c
Center the page in the window, and resets the default resolution.

.TP
.B <
Scale the resolution by 1/1.414

.TP
.B >
Scale the resolution by 1.414

.TP
.B f
Load all the fonts used in the documents.  By default, fonts are loaded
only when needed.

.TP
.B F
Does the same as `f', and precomputes the glyphs of all characters used
in the document.  This takes more time than loading the fonts, but the
pages are drawn faster.

.TP
.B C
Erase the image cache

.RE 
Moreover, the user can drag the currently displayed page in the window
in order to change its relative position.  (This is useful when the
page is displayed at a resolution such that it cannot fit in the
window.)

.SH EYE CANDY MACROS

Using mldvi.sty included this program, you can embed some ActiveDVI
specials into your TeX documents. With ActiveDvi, these specials
provide some eye candy features for your presentation.

.TP
.B \epause
ActiveDvi stops rendering at the point of the document and wait a user key
stroke.

.TP
.B \ewait{sec}
Delay the rendering at the point of the document for sec seconds.

.TP
.B \etag{tag}{text}
Put a "ActiveDVI tag" named tag to the text. This tag can be used to change
the color of the text later.

.TP
.B \ehide{tag}{text}
Same as \etag{tag}{text}, but does not render the text at this point.  You can
display the text later, using \eplay macro.

.TP
.B \eplay{tag}
Display the texts associated with the tag.

.TP
.B \ehilight{tag}{color}
Display the texts associated with the tag, using the color.

.RE
Please look at test/demo.{tex|dvi} and test/macros.{tex|dvi} for
more information and examples.

.SH COPYRIGHT
This program is distributed under the GNU LGPL.
.SH SEE ALSO
.BR latex (1),
.BR kpsewhich (1),
.SH AUTHOR
Mldvi was written by Alexandre Miquel  <Alexandre.Miquel@inria.fr>
and extended in ActiveDVI by Jun Furuse <Jun.Furuse@inria.fr>.
.br
This manual page was written by Sven LUTHER <luther@debian.org>,
for the Debian GNU/Linux system (but may be used by others).

[-- Attachment #3: mldvi.opt.1 --]
[-- Type: text/plain, Size: 17 bytes --]

.so man1/mldvi.1

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Didier Remy]

David Marsal <david.marsal@free.fr> writes:

> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
> creating cache ./config.cache
> checking your compiler package... version 3.04 at /usr/lib/ocaml

Thus. That's the directory where ocaml has installed its library files (It
is bound to CAMLDIR in Makefile.config of advi).  Thus, ocaml should have
copied the files (mlvalues.h, alloc.h, etc.)  in the subdirectory
$CAMLDIR/caml.

> gcc -MM -I/usr/lib/ocaml/caml -I/usr/X11R6/include -O -fno-defer-pop -Wall
> -Wno-unused events.c grY11.c | sed -e 's| /usr/lib/ocaml/caml/[^ ]*||' >>
> .depend
> In file included from events.c:16:
> libgraph.h:19: warning: No include path in which to find mlvalues.h
> events.c:17: warning: No include path in which to find alloc.h
> grY11.c:17: warning: No include path in which to find alloc.h
> grY11.c:20: warning: No include path in which to find fail.h
> In file included from grY11.c:21:
> libgraph.h:19: warning: No include path in which to find mlvalues.h
> ocamlc -g -ccopt "-I/usr/lib/ocaml/caml -I/usr/X11R6/include -O
> -fno-defer-pop -Wall -Wno-unused" -c events.c
> In file included from events.c:16:
> libgraph.h:19: mlvalues.h: No such file or directory
> events.c:17: alloc.h: No such file or directory
> make: *** [events.o] Error 2

These are certainly fatal errors. 
Can you check that the files mlvalues.h, alloc.h fail.h are really in

        /usr/lib/ocaml/caml/

If not, there might be a problem with the ocaml installation.
Otherwise try the simpler command:

        ggc  -I/usr/lib/ocaml/caml -c events.c

on its own.

Didier
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Sven]

On Fri, Jan 25, 2002 at 02:16:57PM +0100, Didier Remy wrote:
> David Marsal <david.marsal@free.fr> writes:
> 
> > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> > 
> > creating cache ./config.cache
> > checking your compiler package... version 3.04 at /usr/lib/ocaml
> 
> Thus. That's the directory where ocaml has installed its library files (It
> is bound to CAMLDIR in Makefile.config of advi).  Thus, ocaml should have
> copied the files (mlvalues.h, alloc.h, etc.)  in the subdirectory
> $CAMLDIR/caml.

No, the include files are in /usr/include/caml on a debian system as the FHS
mandates.

Friendly,

Sven Luther
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Jacques Garrigue]

From: Sven <luther@dpt-info.u-strasbg.fr>

> > > creating cache ./config.cache
> > > checking your compiler package... version 3.04 at /usr/lib/ocaml
> > 
> > Thus. That's the directory where ocaml has installed its library files (It
> > is bound to CAMLDIR in Makefile.config of advi).  Thus, ocaml should have
> > copied the files (mlvalues.h, alloc.h, etc.)  in the subdirectory
> > $CAMLDIR/caml.
> 
> No, the include files are in /usr/include/caml on a debian system as the FHS
> mandates.

That doesn't seem to be a good thing to do.
Objective Caml has only one standard: a unique distribution. If you
start to mess around with the directories, this is not very helpful
for anybody. There is no way a library developper can find the path of
the caml include files, other than expecting them to be in the
standard place, under the library directory. Usually you just call
them by <caml/mlvalues.h>, and your scheme with still work, but if
anybody chooses to do -I`ocaml -where`/caml , which is supposed to be
correct, then it breaks.
And what are you doing with caml-light header files ?

By the way, FHS or not, glib puts parts of its headers in
/usr/local/lib/grealizelib/include, which seems to be pretty similar to what
ocaml does (I noticed that righteous FreeBSD mainteners are moving them
back to /usr/local/include/glib12...)
And these headers will only be used by ocaml programs, this is not
just a standard C library.

Just a comment.

Cheers,

Jacques Garrigue
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Ian Zimmerman]

Sven> No, the include files are in /usr/include/caml on a debian
Sven> system as the FHS mandates.

Jacques> That doesn't seem to be a good thing to do.  Objective Caml
Jacques> has only one standard: a unique distribution. 

So has Debian - that's why it exists at all.  It is one thing that
distinguishes it from e.g. RedHat, which generally just takes the
upstream defaults for configurations, and the result is a mess as one
would expect.

Jacques> If you start to mess around with the directories, this is not
Jacques> very helpful for anybody. 

Yes, it is: to people with experience on Debian, but none on Ocaml.
Which is exactly the sort of people that would install a binary
package, I think.

The way I did it when I built Ocaml from sources was with a symlink,
so that it existed in both places.

BTW, /usr/include/ocaml (to match the package name) would be a better
name. 

-- 
Ian Zimmerman, Oakland, California, U.S.A.
GPG: 433BA087  9C0F 194F 203A 63F7 B1B8  6E5A 8CA3 27DB 433B A087
In his own soul a man bears the source
from which he draws all his sorrows and his joys.
Sophocles.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Jacques Garrigue]

Hello Ian,

> Jacques> If you start to mess around with the directories, this is not
> Jacques> very helpful for anybody. 
> 
> Yes, it is: to people with experience on Debian, but none on Ocaml.
> Which is exactly the sort of people that would install a binary
> package, I think.

The point is that the "right" way to compile an extension to ocaml is
to use ocamlc, which will automatically add /usr/lib/ocaml to the
include path. If the caml subdirectory is not there, this will not be
very useful. Using ocamlc will also set properly some compilation
flags for thread compliance, and make sure you can build a dll.

Since these headers will preferably _not_ be used by gcc directly,
they don't need to be in the standard hierarchy.

Another problem is that both ocaml's (unfortunately limited)
documentation, and ocaml developpers base themselves on a standard
installation. If you start messing around, you end-up with the kind of
quiproquo we are seeing here.

> The way I did it when I built Ocaml from sources was with a symlink,
> so that it existed in both places.

A symlink avoids all these problems. And if you do it yourself, you
know that you're doing something nonstandard, and will no bother the
developpers with this.
 
> BTW, /usr/include/ocaml (to match the package name) would be a better
> name. 

That seems a good idea too.

By the way, all my comments do not intend to criticize the work of
packagers. I know this is a hard task. I just hope we could end up
with a better way to combine efforts.

Jacques Garrigue
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Ian Zimmerman]

Jacques> The point is that the "right" way to compile an extension to
Jacques> ocaml is to use ocamlc, which will automatically add
Jacques> /usr/lib/ocaml to the include path. 

Interesting point.  I have hacked on a few extensions, but I _always_
just called gcc directly.  Somehow the fact that ocamlc is a full
driver just like gcc doesn't easily enter one's consciousness, I'm
afraid.  Also, when one uses things like autoconf and hairy makefile
rules, direct use of the C compiler is more conveient (think of all
the -ccopt stuff you'd have to pass...)

itz> The way I did it when I built Ocaml from sources was with a
itz> symlink, so that it existed in both places.

Jacques> A symlink avoids all these problems. And if you do it
Jacques> yourself, you know that you're doing something nonstandard,
Jacques> and will no bother the developpers with this.

I was suggesting that the link be a part of the package.  Users are
not supposed to touch /usr/include on Debian.

Best regards,

-- 
Ian Zimmerman, Oakland, California, U.S.A.
GPG: 433BA087  9C0F 194F 203A 63F7 B1B8  6E5A 8CA3 27DB 433B A087
In his own soul a man bears the source
from which he draws all his sorrows and his joys.
Sophocles.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Sven]

On Sat, Jan 26, 2002 at 10:45:46AM +0900, Jacques Garrigue wrote:
> Hello Ian,
> 
> > Jacques> If you start to mess around with the directories, this is not
> > Jacques> very helpful for anybody. 
> > 
> > Yes, it is: to people with experience on Debian, but none on Ocaml.
> > Which is exactly the sort of people that would install a binary
> > package, I think.
> 
> The point is that the "right" way to compile an extension to ocaml is
> to use ocamlc, which will automatically add /usr/lib/ocaml to the
> include path. If the caml subdirectory is not there, this will not be
> very useful. Using ocamlc will also set properly some compilation
> flags for thread compliance, and make sure you can build a dll.

I can add a symlink then, if it is agreable.

> Since these headers will preferably _not_ be used by gcc directly,
> they don't need to be in the standard hierarchy.

Well, but people will look there.

> Another problem is that both ocaml's (unfortunately limited)
> documentation, and ocaml developpers base themselves on a standard
> installation. If you start messing around, you end-up with the kind of
> quiproquo we are seeing here.

I will have to patch the documentation then, or better yet add a note about
them.

> > The way I did it when I built Ocaml from sources was with a symlink,
> > so that it existed in both places.
> 
> A symlink avoids all these problems. And if you do it yourself, you
> know that you're doing something nonstandard, and will no bother the
> developpers with this.

I will add a symlink in the next version of the package.

> > BTW, /usr/include/ocaml (to match the package name) would be a better
> > name. 
> 
> That seems a good idea too.

but will break all those #include <caml/xxx.h> :)))

5BTW, i agree, there are lot of caml left around in the ocaml distribution and
friends which could be changed to ocaml.

> By the way, all my comments do not intend to criticize the work of
> packagers. I know this is a hard task. I just hope we could end up
> with a better way to combine efforts.

Okay, i appreciate, i maybe don't all the time see things as fully as i
should, and may ignore problems that you or others may encounter. 

I will add a symlink though, and everybody will be happy.

Friendly,

Sven Luther
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Sven]

On Sat, Jan 26, 2002 at 07:59:21AM +0900, Jacques Garrigue wrote:
> From: Sven <luther@dpt-info.u-strasbg.fr>
> 
> > > > creating cache ./config.cache
> > > > checking your compiler package... version 3.04 at /usr/lib/ocaml
> > > 
> > > Thus. That's the directory where ocaml has installed its library files (It
> > > is bound to CAMLDIR in Makefile.config of advi).  Thus, ocaml should have
> > > copied the files (mlvalues.h, alloc.h, etc.)  in the subdirectory
> > > $CAMLDIR/caml.
> > 
> > No, the include files are in /usr/include/caml on a debian system as the FHS
> > mandates.
> 
> That doesn't seem to be a good thing to do.
> Objective Caml has only one standard: a unique distribution. If you
> start to mess around with the directories, this is not very helpful
> for anybody. There is no way a library developper can find the path of
> the caml include files, other than expecting them to be in the
> standard place, under the library directory. Usually you just call
> them by <caml/mlvalues.h>, and your scheme with still work, but if

Well, yes, that is the intention.

I think there is a symlink from the old place to there. 

> anybody chooses to do -I`ocaml -where`/caml , which is supposed to be
> correct, then it breaks.
> And what are you doing with caml-light header files ?

???

> By the way, FHS or not, glib puts parts of its headers in
> /usr/local/lib/grealizelib/include, which seems to be pretty similar to what
> ocaml does (I noticed that righteous FreeBSD mainteners are moving them
> back to /usr/local/include/glib12...)

You are speaking about  /usr/lib/glib/include/glibconfig.h ?

I don't think this is a header that is supposed to be used for developpment,
is it, while the caml header belong under /usr/include, since they are used in
standard developpment, and you do a #include <caml/mlvalues.h> for them.

> And these headers will only be used by ocaml programs, this is not
> just a standard C library.

Any developper wanting to use C code will need those, thus they go into the
right place, and no need for an additional -I`ocaml -where`/caml, and it will
not break, since the files are where they are supposed to be, in /usr/include.

Just because you are used to doing it like that, doesn't make it the right way
of doing things.

But still, if you have very convincing arguments, i may consider them, i have
not seen such upto now.

Friendly,

Sven Luther
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] Compiler ActiveDVI (CVS)

[Alan Schmitt]

> Comme il va au bout je suis content malgré quelques doutes avec 
> cdk_config et CamlTk

Don't worry about the cdk_config thing, I added that to the ./configure
as I'm a cdk addict (I guess I'm the only one too ;-)

Alan

--
The hacker: someone who figured things out and made something cool happen.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

[Caml-list] CDK support

[Jacques Garrigue]

Hi,

Talking of the CDK, wouldn't it be better to move it to a more
standard framework using findlib and ocamldoc ?

While I'm interested in this effort, requiring downloading and
installing of the whole CDK before being able to use any of its
functionality seems an hindrance, particularly when your architecture
is badly supported by the CDK, and you have to patch your way out.

Also, it should be easy to write makefiles that work both with and
without the tools installed. Well, findlib might be a requirement,
since its functionality is basic enough. A patch on the compiler is
completely impractical when I have to recompile several times a week.

Cheers, and hoping for an even better CDK.

Jacques

From: Alan Schmitt <alan.schmitt@inria.fr>
Subject: Re: [Caml-list] Compiler ActiveDVI (CVS)

> > Comme il va au bout je suis content malgré quelques doutes avec 
> > cdk_config et CamlTk
> 
> Don't worry about the cdk_config thing, I added that to the ./configure
> as I'm a cdk addict (I guess I'm the only one too ;-)
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] CDK support

[Alan Schmitt]

* Jacques Garrigue (garrigue@kurims.kyoto-u.ac.jp) wrote:
> Hi,
> 
> Talking of the CDK, wouldn't it be better to move it to a more
> standard framework using findlib and ocamldoc ?
> 

Why not. I'd need to look at findlib. I should have some time free in a
few months (famous last words ;-)

> While I'm interested in this effort, requiring downloading and
> installing of the whole CDK before being able to use any of its
> functionality seems an hindrance, particularly when your architecture
> is badly supported by the CDK, and you have to patch your way out.
> 

It's true the cdk needs some way to do package management.

> Also, it should be easy to write makefiles that work both with and
> without the tools installed. Well, findlib might be a requirement,
> since its functionality is basic enough. A patch on the compiler is
> completely impractical when I have to recompile several times a week.
> 

If you're talking about a tool that might use the cdk, it's easy (that's
active dvi case). If you're talking about a library that might be
integrated in the cdk, then I think this is related to the package
management issue, and it's a more difficult problem.

> Cheers, and hoping for an even better CDK.
> 
> Jacques

Alan

--
The hacker: someone who figured things out and made something cool happen.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr

Re: [Caml-list] CDK support

[Fabrice Le Fessant]

I agree with you , the CDK needs to be more modular, and to use
ocamldoc. I don't know for findlib, I had a very short look at it, and
found that using my own tool was easier at the beginning. However, I
have no time now for such big changes, I keep updating the CDK with
new ocaml versions, but it's the more I can do these days. If you have
patches for particular architectures, I can apply them on the
distribution so it will be at least a little easier to use.


Best regards,

- Fabrice

-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr