Re: [gentoo-alt] linkage of libiconv on mac os x

[Michael Weiser]

On Thu, Mar 27, 2008 at 06:57:00PM +0100, Fabian Groffen wrote:

> > 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 is exactly the reason we are using wrappers that inject those
> flags.  If gcc and ld aren't first in your default search-path, things
> will get difficult.

Where would I find those wrappers? Because I've just emerge'd glib after
changing into prefix using startprefix which gave me this path:

PATH="/usr/local/gentoo/usr/sbin:/usr/local/gentoo/usr/bin:/usr/local/gentoo/sbin:/usr/local/gentoo/bin:/usr/local/gentoo/opt/bin:/usr/local/gentoo/usr/i686-apple-darwin9/binutils-bin/20080215:/usr/local/gentoo/usr/i686-apple-darwin9/gcc-bin/4.0.1:/usr/sbin:/usr/bin:/sbin:/bin"

and those binaries:

root@esgaroth:/usr/local/gentoo/usr/bin $ which gcc
/usr/local/gentoo/usr/bin/gcc
root@esgaroth:/usr/local/gentoo/usr/bin $ which i686-apple-darwin9-gcc
/usr/local/gentoo/usr/bin/i686-apple-darwin9-gcc
root@esgaroth:/usr/local/gentoo/usr/bin $ which ld
/usr/local/gentoo/usr/bin/ld

and I still get:

michael@esgaroth:~ # otool -L /usr/local/gentoo/usr/lib/libglib-2.0.dylib 
/usr/local/gentoo/usr/lib/libglib-2.0.dylib:
	/usr/local/gentoo/usr/lib/libglib-2.0.0.dylib (compatibility version 1601.0.0, current version 1601.1.0)
	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/usr/local/gentoo/usr/lib/libintl.8.dylib (compatibility version 9.0.0, current version 9.1.0)
	/usr/local/gentoo/usr/lib/gcc/i686-apple-darwin9/4.0.1/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0)
-- 
bye,
Micha
-- 
gentoo-alt@l.g.o mailing list