Daniel Macks wrote: > Could someone(s) test the libiconv in my cvs exp? Goal: compare build > transcript: > > 1) with fink libiconv-dev installed, > 2) without libiconv-dev, > 3) without libiconv-dev *and with /usr/include/iconv.h and > /usr/lib/libiconv.dylib (and .la if present) moved away. > > Need to make sure we aren't getting circular dependency and aren't > mixing system with internal lib/headers of same name. Clean on 10.4, > need checked on 10.6/32 and 10.6/64 > > http://fink.cvs.sf.net/viewvc/*checkout*/fink/experimental/dmacks/finkinfo/libiconv.info?revision=1.2 > http://fink.cvs.sf.net/viewvc/*checkout*/fink/experimental/dmacks/finkinfo/libiconv.patch?revision=1.1
No problem here on 10.6/64. The only difference in the build logs is a line libtool: install: warning: `../lib/libiconv.la' has not been installed in `/sw/lib' that appears when libiconv is built while libiconv-dev is not installed. This seems to indicate that when libiconv-dev is installed, the build process sees at this point the installed /sw/lib/libiconv.la and not the newly-built ../lib/libiconv.la. But why it looks at libconv.la at this point at all is unclear. This is between the two lines /bin/sh ../libtool --mode=install /usr/bin/install -c iconv /sw/src/fink.build/root-libiconv-1.12-4/sw/bin/iconv and /usr/bin/install -c .libs/iconv /sw/src/fink.build/root-libiconv-1.12-4/sw/bin/iconv just after the linking of the iconv executable is done, which for some strange reason happens during the install phase. -- Martin ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
