t1lib: unable to infer tagged configuration (was: Re: xpdf install failed)

Ryan Schmidt ryandesign at macports.org
Sat Sep 13 00:02:40 PDT 2008

On Sep 12, 2008, at 5:10 AM, Joerg van den Hoff wrote:

>> In particular, this problem showed up a lot when libtool was built
>> *before* MacPorts started using /usr/bin/gcc-4.0 as CC (instead of  
>> just
>> "gcc" or "cc"), and you attempted to build certain ports *after*
>> updating MacPorts. However, this change was a long time ago so I'm
>> surprised you're still running into it. Try the above and let us know
> I try to keep port itself and "important" packages (or those which are
> developing rapidly) up to date, but are otherwise content if  
> 'outdated'
> packages are running just fine. I rely on ports to detect things which
> must be updated due to dependencies. so I naively would have thought
> that if, e.g. xpdf depdends on libtool and that one is to old, it  
> should
> have been updated first automatically? where's my error here?

I'm not sure. Possibly nothing. I haven't gone back to test whether  
MacPorts properly attempts to upgrade dependencies before upgrading  
the port you requested.

More information about the macports-users mailing list