Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <3B7AFEF9.8070400@ece.gatech.edu> Date: Wed, 15 Aug 2001 19:00:09 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713 X-Accept-Language: en-us MIME-Version: 1.0 To: Charles Wilson CC: cygwin-developers AT cygwin DOT com Subject: Re: Does CVS build? References: <20010815132450 DOT A1468 AT dothill DOT com> <3B7AEC05 DOT 7FBF0C8C AT yahoo DOT com> <20010815155157 DOT B20199 AT redhat DOT com> <20010815162916 DOT A28118 AT redhat DOT com> <20010815171031 DOT A29030 AT redhat DOT com> <3B7AE8D7 DOT 7050508 AT ece DOT gatech DOT edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Charles Wilson wrote: >> If can get verification that this works, I'll check it into sourceware. > > Well, right now autoconf is complaining: > > configure.in:297: error: possibly undefined macro: AC_PROG_CC_WORKS > configure:1304: error: possibly undefined macro: AC_PROG_CC_G > configure:1296: error: possibly undefined macro: AC_PROG_CC_GNU > > I ran autoconf (2.52) in the libiberty source directory only, not > anywhere else. I think this is one of the autoconf-2.13 vs. 2.5x > problems. Well, I've come up with a patch that seems to work when you autoconf libiberty with autoconf-2.52 and takes care to remain compatible with 2.13. (Compiling the dll is successful, too). Unfortunately, I can't do a 'cvs diff' since sourceware is hammered right now (load average of 159). I'll try again after dinner. --Chuck