On Wed, Oct 03, 2007 at 09:59:10AM +0900, paul fons wrote:
> 
> > ...the actual problem you're having is with the popt package.
> >
> > What version of the "gettext-tools" package do you have installed?
> > Does reinstalling it ('fink reinstall gettext-tools') solve the
> > building of the popt package?
> $fink list gettext-tools
> Information about 6561 packages read in 1 seconds.
>   i   gettext-tools    0.14.5-3     GNU Internationalization utils  
> (shared libs)

Ahh, there's your response...sorry if previous email was snide.

> Rebuilding gettext-tools works without problem and gives the same  
> version information.  After this attempting to install popt gives an  
> undefined symbol error in the automake process (output pasted  
> below).  I am confused as to what to try next.  Fink is using the  
> developer tools autoreconf I assume.  I note that the version of the  
> autoreconf tool I have is "autoreconf (GNU Autoconf) 2.6".  I note  
> that this is different than my powerpc system (which uses 2.59).  I  
> suspect that I many be a victim of the Xtools beta for Lepoard that I  
> installed a while ago from ADT.  Is this autoreconf broken?  If this  
> is the case what is the best countermeasure -- should I install the  
> older version of the developer tools from Apple's developer site.  It  
> is too bad that things are so fragile.

Yeah, autotools are a whole bunch of small things that have to be in
sync (or at least "as expected") to work together correctly. The popt
package attempts to specify these explicitly, and when there's no
interference from other things, we know it works. We don't know what
"other things" matter, but scattered reports of this problem, so
*something* matters. Having mismatched XCode vs your system is a bad
idea for many reasons, not sure it affects this particular problem.

I think there are ways we can include the AM_GNU_GETTEXT macro in the
popt package itself. I looked at upgrading popt recently (the new
version does just that), but it's probably going to be messy and I
don't see an urgent need to upgrade. Maybe should import just the
macro support fix.

dan

-- 
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to