X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Vadim Zeitlin <vz-cygwin AT zeitlins DOT org>
Subject: Re: m4 1.4.16-1 doesn't seem to work
Date: Fri, 17 Jun 2011 18:47:58 +0000 (UTC)
Lines: 20
Message-ID: <loom.20110617T204517-579@post.gmane.org>
References: <19921 DOT 30753 DOT 62000 DOT 974121 AT gargle DOT gargle DOT HOWL> <4DD293E4 DOT 2070407 AT redhat DOT com> <19922 DOT 61962 DOT 640000 DOT 987645 AT gargle DOT gargle DOT HOWL> <4DD2F7C1 DOT 1010205 AT redhat DOT com> <19922 DOT 64949 DOT 62000 DOT 98452 AT gargle DOT gargle DOT HOWL> <loom DOT 20110617T190806-423 AT post DOT gmane DOT org> <20110617172911 DOT GB26670 AT jethro DOT local DOT lan>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

David Sastre <d.sastre.medina <at> gmail.com> writes:

> On Fri, Jun 17, 2011 at 05:16:02PM +0000, Vadim Zeitlin wrote:
> >  So it seems to me that there is a real problem with m4 1.4.16.
> > Unfortunately I don't know how to debug it further. For the moment I'm just
> > going to stay with 1.4.15 but if anybody has any ideas for further tests
> > I'd be glad to perform them and post the results.
> 
> You could download the source package, build it and try to see if it
> makes a difference. Just an idea.

 Thanks, I didn't think about this. I guess I'd need to built it in exactly
the same way as the binary packages are built though as the problem should
be in the build step (it's hard to believe that m4 1.4.16 would be broken
on its own...) and I'm not sure how to do it -- but I'll try to learn.

 Regards,
VZ




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple