Hello,
I noticed that quite a number of binaries and libraries in my prefix
installation are linked against /usr/lib/libiconv.2.dylib as well as
${EPREFIX}/usr/lib/libiconv.2.dylib. My system is Mac OS X 10.5.2.
The cause seems obvious: If some package doesn't add
-I${EPREFIX}/usr/include and -L${EPREFIX}/usr/lib to its CFLAGS and
LDFLAGS, it will link against the system's libiconv. If this package
happens to be a library like glib, it pulls it into all the binaries
that link against it.
This hasn't caused any problems thus far but I'm wondering if this is
known behaviour or a bug in my setup.
--
Thanks in advance,
Micha
--
[email protected] mailing list
