Re: [Fink-users] issues with libiconv.la 10.6

[Alexander Hansen]

Andrew Hartung wrote:
> I'm getting multiple build failures from packages such as pycairo- 
> py26-1.8.8-2 and gtk+2 that end with something like the following:
> 
> grep: /usr/lib/libiconv.la: No such file or directory
> sed: /usr/lib/libiconv.la: No such file or directory
> libtool: link: `/usr/lib/libiconv.la' is not a valid libtool archive
> make[2]: *** [_cairo.la] Error 1
> make[1]: *** [all] Error 2
> make: *** [all-recursive] Error 1
> ### execution of make failed, exit code 2
> Removing runtime build-lock...
> Removing build-lock package...
> /sw/bin/dpkg-lockwait -r fink-buildlock-pycairo-py26-1.8.8-2
> (Reading database ... 108576 files and directories currently installed.)
> Removing fink-buildlock-pycairo-py26-1.8.8-2 ...
> Failed: phase compiling: pycairo-py26-1.8.8-2 failed
> 
> 
> The common point being the libiconv.la reference.
> 
> I'm running 10.6.1 on a Mac pro.
> 
> I followed the instructions to upgrade to 10.6 on the main page, but  
> before I did it in the way it listed(and had even seen the  
> instructions), I had run a self-update which seem to do a big upgrade.  
> When I then did the upgrade as suggested the process seemed to do  
> nothing new. I don' t know if this matters or not.
> 
> Package manager version: 0.29.9
> Distribution version: selfupdate-rsync Fri Sep 11 22:23:26 2009, 10.6,  
> i386
> 
> Also, when I run a self-update, all of the trees say:
> 
> rsync -rtz --delete-after --delete -q   --include='10.4/' -- 
> include='10.4/stable/' --include='10.4/stable/main/' --include='10.4/ 
> stable/main/finkinfo/' --include='10.4/stable/main/finkinfo/*/' -- 
> include='10.4/stable/main/finkinfo/*' --include='10.4/stable/main/ 
> finkinfo/**/*' --include='10.4/' --include='10.4/stable/' -- 
> include='10.4/stable/crypto/' --include='10.4/stable/crypto/finkinfo/'  
> --include='10.4/stable/crypto/finkinfo/*/' --include='10.4/stable/ 
> crypto/finkinfo/*' --include='10.4/stable/crypto/finkinfo/**/*' -- 
> include='10.4/' --include='10.4/unstable/' --include='10.4/unstable/ 
> main/' --include='10.4/unstable/main/finkinfo/' --include='10.4/ 
> unstable/main/finkinfo/*/' --include='10.4/unstable/main/finkinfo/*' -- 
> include='10.4/unstable/main/finkinfo/**/*' --include='10.4/' -- 
> include='10.4/unstable/' --include='10.4/unstable/crypto/' -- 
> include='10.4/unstable/crypto/finkinfo/' --include='10.4/unstable/ 
> crypto/finkinfo/*/' --include='10.4/unstable/crypto/finkinfo/*' -- 
> include='10.4/unstable/crypto/finkinfo/**/*' --include='VERSION' -- 
> include='DISTRIBUTION' --include='README' --exclude='**' 'rsync:// 
> distfiles.master.finkmirrors.net/finkinfo' '/sw/fink/'
> 
> 
> Should these be/are there 10.5 trees that should be here?
> 
> I've gone from a 500 Mhz G4 to a 8 core Mac Pro just this year(just a  
> bit of an upgrade), so I haven't been following the latest fink news  
> and was running 10.4.x on the old G4. I didn't copy /sw from the old  
> computer and rebuilt everything(was a mite bit faster on the Pro vs  
> the G4), but as I used Apple's migration utility when I got the Pro, I  
> wonder if there is an old configuration file somewhere outside the /sw  
> directory that might be causing an issue too.
> 
> 
> A final question:
> 
> I'd like to go 64 bit with fink; is there somehow I can check to see  
> what packages are available for 64 bit? There are a couple I must have  
> and would have to stick with 32 bit for now if they are not available.
> 
> 

What's going on here is that something in the build chain for the
packages you're trying to install was built against the system's
libiconv instead of ours--ideally we'd like packages not to do that, but
they don't always get caught.  In doing so, it encoded the location of a
libtool archive file for that library.  Unfortunately, Apple decided to
get rid of the .la file in question for 10.6.

Try the following:

        find /sw/lib -name *.la | xargs grep -l /usr/lib/libiconv.la

to locate any references to /usr/lib/libiconv.la

Looking at my own system, it appears that a good number of cases will
have both /usr/lib/libiconv.la and /sw/lib/libiconv.la on the
dependency_libs line.  I'll see if I can work up a handy-dandy regex for
such a case, but I've gotta run.

-- 
Alexander Hansen
Fink User Liaison


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users