Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<3CD0AC70.4050909@ece.gatech.edu>
Date:	Wed, 01 May 2002 23:03:12 -0400
From:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Updated: pkgconfig-0.12.0-1
References:	<3CD09661 DOT 8040506 AT ece DOT gatech DOT edu>

 > that I wondered whether the buggy m4
 > macro code that makes it work (theoretically) with
 > autoconf, has been fixed.

Actually, the code you excerpted was generated by this stanza in the 
pkg.m4 file:

   if test -z "$PKG_CONFIG"; then
     AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
   fi

So, really, the problem is how *autoconf* expands/defines the 
AC_PATH_PROG macro.  Cygwin has recently updated to autoconf-2.53, maybe 
the code genereated by 2.53 is more to your liking?

Anyway, I think this is an autoconf issue, not a pkgconfig one.  So, the 
appropriate ChangeLogs to search would be the autoconf ones.

Hope that helps...

--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -