X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-Id: <1228854443.32401.1289162749@webmail.messagingengine.com> From: "Charles Wilson" To: cygwin AT cygwin DOT com Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 Subject: Re: Latest autoconf (2.63): problem generating libtool script when reconfiguring GCC (maybe others). Date: Tue, 09 Dec 2008 15:27:23 -0500 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 As pointed out downthread, the gcc tree doesn't actually support using newer autotools. Current efforts to future-proof gcc's build machinery, and thus make it easier to move officially to 2.6x at some point in the future, are still in work. I have the following two packages on my box: gcc-autoconf and gcc-automake [*], which: (1) are pristine versions of ac-2.59 and am-1.9.6 with no cygwin-specific code changes (2) install into /opt/gcc-tools/{bin|share} (3) /opt/gcc-tools/share/aclocal-1.9/dirlist specifies /usr/share/aclocal/ so as to "find" .m4 files from gettext, libiconv, libtool, etc. That way, when I'm mucking about with gcc and need to regen the auto* stuff, I can just set $PATH appropriately. Would there be interest in pushing these packages into the distro? [*] I think that's what I called them. Maybe it was auto*-gcc. I can't reach my box right now... -- 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/