My previous comments were unclear because my original text was 
cut out. Here I patch it below. 

On Fri, Dec 25, 2009 at 11:47:09AM +0100, Martin Costabel wrote:
> pavicic wrote:
>> On Thu, Dec 24, 2009 at 12:36:40PM +0100, Martin Costabel wrote:
>>> pavicic wrote:
>>> []
>>>> Yes, I'm deleting all *.la files in /sw/lib and all its 
>>>> subdirectories  but that doesn't help. 
>>>>
>>>> grep: /sw/lib/libiconv.la: No such file or directory
>>> Then look in /usr/local/lib or elsewhere. It is an *.la file on 
>>> *your*  computer that contains the reference to the non-existing   
>>> /sw/lib/libiconv.la.
>>>
>>
>> Finder gives nothing.  
>>
>> Also neither 
>>
>> find / -name libiconv.la
>
> This has been discussed on the lists so often in the past months that I  
> didn't think it necessary to explain once more. Here goes:
>
> The error you are getting comes from the fact that some *other* "libtool  
> archive" file, that is, a file with extension ".la", contains a line
>
> dependency_libs=' ... /sw/lib/libiconv.la ... '
>
> You have to find that file which, unfortunately, is not indicated in the  
> error message (a regrettable shortcoming of libtool) and remove it or,  
> better, edit it and remove everything in the dependency_libs list, so  
> that the line reads
>
> dependency_libs=''

As I wrote before I scanned all the files on my computer and there 
is no explicit reference to /sw/lib/libiconv.la
The reference which appear at the end of "fink update-all" must 
be geerated in some other more involved way and not because there 
already is a mismatched reference to /sw/lib/libiconv.la
in some existing file. There is no any reference to /sw/lib/libiconv.la
except those that I stated below.

Finder gives nothing.                                                           
                   
                                                                                
                   
Also neither                                                                    
                   
                                                                                
                   
find / -name libiconv.la                                                        
                   
                                                                                
                   
nor                                                                             
                   
                                                                                
                   
find / -name \*libiconv\*la\*                                                   
                   
                                                                                
                   
gives anything.                                                                 
                   
                                                                                
                   
But isn't "grep" suggesting that the program is trying to find                  
                   
libiconv.la in some configuration file or so, but can't?                        
                   
                                                                                
                   
libiconv.la is mentioned in libiconv.patch twice:                               
                   
                                                                                
                   
-         *) $(LIBTOOL_LINK) $(CC) $(LDFLAGS) $(CFLAGS) $(iconv_LDFLAGS)        
                   
          ico...@objext@ ../srclib/libicrt.a                                    
                   
$(DESTDIR)$(libdir)/libiconv.la @LTLIBINTL@ $(objects_r...@woe32@) -o           
                   
iconv;; \                                                                       
                   
+     *) $(LIBTOOL_LINK) $(CC) $(LDFLAGS) $(CFLAGS) $(iconv_LDFLAGS)            
                   
ico...@objext@ ../srclib/libicrt.a ../lib/libiconv.la @LIBINTL_STATIC@          
                   
$(objects_r...@woe32@) -o iconv;; \                                             
                   
                                                                                
                   
Apart from libiconv.info this is the only file where libivonv.la is             
                   
explicitely mentioned.                                                          
                   
                                                                                
                   
Mladen.            

> The *.la files are text files which can be edited with any standard text  
> editor (with admin privileges).
>
> The error message talks about "grep" and "sed", because libtool uses  
> these tools to extract the dependency_libs list from the *.la file.
>
> A final explanation about the origin of the error: When that (as yet  
> unknown) *.la file containing the reference to /sw/lib/libiconv.la was  
> created during the build process of some other package, the file  
> /sw/lib/libiconv.la *did* exist on the computer. Then it was removed,  
> following advice smilar to what I gave above, namely to remove all *.la  
> files inside /sw/. The latter advice was published as a reaction to the  
> fact that Apple removed their *.la files inside /usr/lib on Snow Leopard  
> and everybody who upgraded their Fink from Leopard to Snow Leopard was  
> getting these same errors.

Yes, and following that advice I deleted /sw/lib/libiconv.la as  well. 
But perhaps a remedy is to get libiconv.la from somewhere. 

Mladen.


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to