From: Jun.Furuse@inria.fr
To: "chris.danx" <chris.danx@ntlworld.com>
Cc: "Gurr, David (MED, self)" <David.Gurr@med.ge.com>,
Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Building camlimages programs on deb (and linux)
Date: Mon, 24 Nov 2003 21:46:06 +0100 [thread overview]
Message-ID: <lwd6bhjy0h.wl@inria.fr> (raw)
In-Reply-To: <3FC2528E.60506@ntlworld.com>
Hello,
> ocamlc `camlimages-config` -cclib "-L/usr/X11R6/lib -lxvthumb -lXpm
> -lX11 -lpng -lfreetype -lz -ljpeg -lgif"
Duh, I cannot tell what is wrong. Even we, the authors, do not know
about the script "camlimages-config". It is not from the official
camlimages distribution. (I guess it comes from Debian package, which
is out of my control.)
I always use $(CAMLIMAGESLIBS) defined inside
/usr/local/lib/ocaml/camlimages/Makefile.config for linking the
camlimages to my programs. It should list all the libraries required.
BTW, it sounds still strange that you fail to link even with -lX11.
Please send me what happens (including error messages) if you execute
the following:
ocamlc -custom -verbose `camlimages-config`
-cclib "-L/usr/X11R6/lib -lxvthumb -lXpm
-lX11 -lpng -lfreetype -lz -ljpeg -lgif"
> If i leave ci_xpm.cma off, it links. I don't know if it's safe to leave
> it off. I suppose if I don't use XPM it'll be ok, but it's not the
> greatest solution.
Camlimages libraries are separated into pieces so that you can link
the libraries you really want. If you are not interested to read/write
xpm images in your program, you need not to link ci_xpm.cma.
Anyway, you found a bug of camlimages. Usually Xpm requires X11, but I
forgot to link it. I will fix the problem.
--
Jun
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-11-24 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D4DBD8568F05D511A1C20002A55C008C11AC0796@uswaumsx03medge.med.ge.com>
2003-11-24 18:48 ` chris.danx
2003-11-24 20:46 ` Jun.Furuse [this message]
2003-11-24 23:02 ` chris.danx
2003-11-25 10:42 ` Jun.Furuse
2003-11-24 0:27 chris.danx
2003-11-24 1:08 ` Issac Trotts
2003-11-24 17:34 ` chris.danx
2003-11-24 18:50 ` Matt Gushee
2003-11-24 19:10 ` chris.danx
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=lwd6bhjy0h.wl@inria.fr \
--to=jun.furuse@inria.fr \
--cc=David.Gurr@med.ge.com \
--cc=caml-list@inria.fr \
--cc=chris.danx@ntlworld.com \
/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