From: Christophe Raffalli <Christophe.Raffalli@univ-savoie.fr>
To: "Daniel Bünzli" <daniel.buenzli@epfl.ch>
Cc: caml-list caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] OS X and camlimages
Date: Tue, 07 Dec 2004 18:15:13 +0100 [thread overview]
Message-ID: <41B5E521.2020001@univ-savoie.fr> (raw)
In-Reply-To: <59134186-47DC-11D9-9DB0-000393DBC266@epfl.ch>
[-- Attachment #1: Type: text/plain, Size: 2567 bytes --]
Daniel Bünzli wrote:
>
> Le 6 déc. 04, à 22:57, Christophe Raffalli a écrit :
>
>
>> * I failed to compile cleanly camlimages on OS X (with fink) (I had to
>> add -L/
>> sw/lib and -I/sw/include at the proper places ...
>
>
> Maybe this should be documented in the INSTALL file :
>
> > ./configure --help
> [...]
> Some influential environment variables:
> CC C compiler command
> CFLAGS C compiler flags
> LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
> nonstandard directory <lib dir>
> CPPFLAGS C/C++ preprocessor flags, e.g. -I<include dir> if you have
> headers in a nonstandard directory <include dir>
> CPP C preprocessor
>
>
Thanks.
>> * By the way, do you know if and what part of camlimages can be
>> compiled on
>> OS X without any fink library.
>
>
> Here, with X11 and ghostscript installed, configure ends with :
>
> External libraries: lablgl bmp ppm xpm freetype(2) ps
So you say no way to have png, tiff jpeg in standrad apple SDK ?
>> ld: warning multiple definitions of symbol _png_get_uint_31
>> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit(single
>> module) definition of _png_get_uint_31
>> /sw/lib/libpng.dylib(pngrutil.pic.o) definition of _png_get_uint_31
>
>
> I don't think libpng is present on the system, it is not in /usr/lib.
> And if you look at
> the output of
>
> > otool -L /System/Library/Frameworks/AppKit.framework/AppKit
>
> you will see that the AppKit is not dynamically linked against any
> libpng. If you grep for 'png' in the output of
>
> > nm /System/Library/Frameworks/AppKit.framework/AppKit
I did all that, but still there seems to be a name collison between
AppKit and libpng, while no png is listed in the header.
> you'll see the symbols of png's api so it must be statically linked in
> the Appkit.
If true, that's a pity.
> Greetings,
>
> Daniel
>
> P.S. More about that warning in man ld
>
You mean a way to choose which one you want to use ? I will have a look.
Thanks.
--
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex
tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI
---------------------------------------------
IMPORTANT: this mail is signed using PGP/MIME
At least Enigmail/Mozilla, mutt or evolution
can check this signature. The public key is
stored on www.keyserver.net
---------------------------------------------
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2004-12-07 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 21:57 Christophe Raffalli
2004-12-06 23:12 ` [Caml-list] " Daniel Bünzli
2004-12-07 17:15 ` Christophe Raffalli [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=41B5E521.2020001@univ-savoie.fr \
--to=christophe.raffalli@univ-savoie.fr \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@epfl.ch \
/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