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 Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3C8C5198.2020700@ece.gatech.edu> Date: Mon, 11 Mar 2002 01:41:28 -0500 From: Charles Wilson 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 CC: James Harvey Subject: Re: autoconf 2.52a-1: M4PATH not being honoured through wrapper script. References: <014001c1be21$81475b20$898717ac AT grimsby> <3C81C56A DOT 3080802 AT ece DOT gatech DOT edu> <12b501c1c429$9c8464b0$898717ac AT grimsby> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit James Harvey wrote: > OK, thanks. A colleague of mine noticed a bug, in that: > > export M4PATH=${AUTO_STABLE}/share/autoconf:${M4PATH} > > will set M4PATH to '/foo/share.autoconf:' if it was not previously set, and > an empty path equates to the current directory, which is probably not what > was intended. How do you figure that? "/foo/share/autoconf:" contains only a single directory. It is not equivalent to "/foo/share/autoconf:." Anyway, it doesn't really matter -- m4 *always* searches the current working directory, regardless of the value of ${M4PATH} or the use of -I options. See 'info m4'. > This really needs a check to see whether M4PATH was previously > set, and only appending to it if so. This isn't an issue for PATH because > you assume it is always set to something. I don't think it's an issue for M4PATH, either. (OTOH, your *other* bugreport is a valid concern, and I'm fixing that now...) --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/