libtool woes

[Ryan Schmidt]

On Feb 4, 2008, at 07:33, David.Epstein at warwick.ac.uk wrote:

> Ryan Schmidt wrote:
>
>> So based on the fact that you experienced the error without libtool
>> installed, and that Peter O'Gorman says it may be that apr was built
>> before MacPorts 1.6 was released, it sounds like maybe apr, and not
>> libtool, was the problem. I originally suggested that one or the
>> other of those ports was the problem but I have yet to hear anyone
>> definitively say which one it is. Simply force-upgrading both doesn't
>> help us isolate the problem. :)
>>
>> I note that in your output above, you're uninstalling apr 1.2.11_0.
>> That's an old version anyway. The current version is 1.2.12_0. So you
>> should try uninstalling libtool, then upgrading apr, then see if it
>> works.
>
> Quoted from:  http://www.nabble.com/libtool-woes- 
> tp15248567p15267463.html
>
> Is a simple uninstall good enough for your purposes, or do I need  
> to do a clean first?
>
> I am about to go into the University where I have another Mac with  
> the same problem.
> I will record version numbers of the various items, upgrade apr, do  
> nothing about libtool,
> and report on what happens.

For the same error experienced with the mjpegtools port in ticket  
#13648, I have bumped the revision of the libtool port, so that  
everyone is forced to rebuild it. And in ticket # I have suggested  
that the revision of the apr port be bumped, too, and assigned it to  
apr's maintainer. That should fix it. Hopefully.

Until that gets pushed through, you should be able to clean and force  
upgrades of apr and/or libtool.

If you have apr installed:

sudo port clean --work apr
sudo port -ncuf upgrade apr

If you have libtool installed:

sudo port clean --work libtool
sudo port -ncuf upgrade libtool