On Tuesday 05 June 2001 1:04 am, Robert Collins wrote:
I added AC_REQUIRE([AC_PROG_CC])dnl to
/usr/share/autoconf/acspecific.m4, and it made no difference at all. I
did several variations-on-a-theme, with no luck.
Adding
AC_EXEEXT immediately _after_ the AC_PROG_CC line in configure.in for
- Original Message -
From: Gary V. Vaughan [EMAIL PROTECTED]
To: Robert Collins [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, June 05, 2001 6:51 AM
Subject: Re: cygwin libtool breakage
On Monday 04 June 2001 2:22 am, Robert Collins wrote
- Original Message -
From: Robert Collins [EMAIL PROTECTED]
- Original Message -
From: Gary V. Vaughan [EMAIL PROTECTED]
On Monday 04 June 2001 2:22 am, Robert Collins wrote:
-Original Message-
From: Gary V. Vaughan [mailto:[EMAIL PROTECTED]]
Robert Collins wrote:
I _did_ have autoconf CVS HEAD at one point, I reverted to 2.13 to be in
line with other users, and I haven't upgraded again yet. I don't recall
this problem from back then.. if that helps at all :]
Rob
Hi Robert,
Don't know if you follow the autoconf list but you
-Original Message-
From: Earnie Boyd [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 05, 2001 10:55 AM
To: Robert Collins
Cc: Gary V. Vaughan; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: cygwin libtool breakage
Robert Collins wrote:
I _did_ have autoconf CVS HEAD
On Monday 04 June 2001 2:22 am, Robert Collins wrote:
-Original Message-
From: Gary V. Vaughan [mailto:[EMAIL PROTECTED]]
gary@MALACHI ~/libtool$ export CC=gcc
I haven't done this... can the cygwin environment test ac_require
ac_prog_cc ?
In autoconf-2.13 it should have done:
