On Thursday, September 26, 2002, at 02:18 PM, Chris wrote: > I checked, and the perl-edited Makefile.PL does have ['-liconv'] in it > ... do I need to do something to convince the makefile to look in the > right place? libiconv.dylib ended up where it needed to be, so the > environment looks OK. Do I need to recompile Perl 5.8.0 with liviconv > to prevent these _libiconv* undefined symbol errors? The page at > http://david.wheeler.net/osx.html seems to depict this "just working", > though, which confuses me. Have things changed since the page was > written? > > Or is this evidence I've badly hozed something??
No. What most likely happened is that you compiled Perl 5.8.0 in /usr/local before you compiled anything else there. libiconv.dyld would have been installed in /usr/local/lib, but if that directory didn't exist when you compiled Perl, then Perl doesn't know to look there for libraries. You have two options, one that I've tried and one that I haven't. The first is to simply reconfigure and recompile Perl now that you have /usr/local/lib. Then it should do the right thing. The other option (untested) is to add /usr/local/lib to the relevant Config.pm hash value. I have no idea if that'll work or not. It's to get around this problem that Bricolage's README.MacOSX recommends that you compile libexpat before you do anything else, as this will create /usr/local/lib. It seems to me that if you configure Perl with -Dprefix=/usr/local, it should be set up to look for libraries in /usr/local/lib, anyway, since that's where Perl will put it's own modules! But it doesn't so you have to make them yourself. HTH, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
