Message-ID: <20090207100957.2548@blackhawk>
Date: Sat, 07 Feb 2009 10:09:57 +0900
From: wynfield@gmail.com
To: <cygwin@cygwin.com>
Subject: Re: how to install libtoolize
In-reply-to: Your message of Thu, 05 Feb 2009 22:53:55 -0500 	 <498BB453.8080401@cygwin.com>
References: <498AB8F6.5060906@gmail.com> 	 <195b3f1f0902051921m7a3400bfh7e8a2e753da3d074@mail.gmail.com> 	 <498BB453.8080401@cygwin.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com


Re:
>Larry Hall (Cygwin) <reply-to-list-only-lh@cygwin.com> wrote:
> On 02/05/2009, Wynfield Henman wrote:
> > Though I am building a different package, I have the same problem as
> > mentioned below.  The libtool package downloaded is 46 bytes
> > (effectively null) and get stashed into the _obsolete folder without
> > ever getting installed.
> <http://cygwin.com/cgi-bin2/package-grep.cgi?grep=usr%2Fbin%2Flibtoolize>
> 
> Don't install obselete packages unless you really know what you're doing.
> 
> Given the above, why doesn't just installing the 'libtool' package get
> you what you need?
> 

That is just the problem it doesn't get what is needed, but only shows the obsolete (from what you say) versions as the newest. 

I even tried experimental to try to find newer libtool version, but none show up.
Version1.5b or whatever was presented as the newest version by setup.

There was no intentional _obsolete gets on my part.
I solved the problem by hand getting the new vesion and untarring it in the appropriate location, but that shouldn't have to be done. 

I believe it is a setup related problem, either hints or ini file data.

Regards
> -- 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/