X-Spam-Check-By: sourceware.org Message-ID: <44E14F7D.8040509@cwilson.fastmail.fm> Date: Tue, 15 Aug 2006 00:37:17 -0400 From: Charles Wilson User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: autom4te-2.13 missing in autoconf2.1-2.13-1 References: <44DA14C6 DOT 9080206 AT x-ray DOT at> In-Reply-To: <44DA14C6.9080206@x-ray.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reini Urban wrote: >> autoconf2.1-2.13-1 > > This package misses /usr/bin/autom4te-2.13 > resp. the wrapper has no extra logic for the missing autom4te. > > I solved it by > cp /usr/bin/autom4te-2.5x /usr/bin/autom4te-2.13 > Strangely this was the first time I needed such an old cruft, for catdoc. autoconf-2.13 does not have and never has had an autom4te. Thus, there's nothing to wrap -- and copying the 2.5x version is certainly wrong -- because now aclocal will invoke autoconf-2.5x operations on a 2.13-specific project. So PLEASE remove this guaranteed-to-break-stuff suggestion from your catdoc README: test -e /usr/bin/autom4te-2.13 || ln -s /usr/bin/autom4te-2.5x /usr/bin/autom4te-2.13 The real reason you got an error is described in this thread: "Ping autoconf maintainer (was Re: auto tools issues)" http://www.cygwin.com/ml/cygwin/2005-07/msg00352.html I encourage you to read the whole thing. (A possible workaround for your problem in building catdoc is to have your cygport script create a symlink within your build directory: aclocal -> /usr/bin/aclocal-${VER}, and then put the builddir in front of the PATH. This has the advantage of not permanently modifying the the regular cygwin environment just for catdoc-building) -- Chuck -- 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/