From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26682 invoked by alias); 18 Oct 2010 14:27:28 -0000 Received: (qmail 26553 invoked by uid 22791); 18 Oct 2010 14:27:25 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from mail-px0-f169.google.com (HELO mail-px0-f169.google.com) (209.85.212.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 18 Oct 2010 14:27:13 +0000 Received: by pxi6 with SMTP id 6so250248pxi.0 for ; Mon, 18 Oct 2010 07:27:11 -0700 (PDT) Received: by 10.142.221.19 with SMTP id t19mr3446715wfg.235.1287412031839; Mon, 18 Oct 2010 07:27:11 -0700 (PDT) Received: from bubble.grove.modra.org ([115.187.252.19]) by mx.google.com with ESMTPS id p8sm23028840wff.4.2010.10.18.07.27.07 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 18 Oct 2010 07:27:08 -0700 (PDT) Received: by bubble.grove.modra.org (Postfix, from userid 1000) id 488B2170C206; Tue, 19 Oct 2010 00:56:55 +1030 (CST) Date: Mon, 18 Oct 2010 14:27:00 -0000 From: Alan Modra To: Ralf Wildenhues , gcc-patches@gcc.gnu.org, binutils@sourceware.org Subject: Re: PR binutils/12110 spaces in source path Message-ID: <20101018142653.GI26553@bubble.grove.modra.org> Mail-Followup-To: Ralf Wildenhues , gcc-patches@gcc.gnu.org, binutils@sourceware.org References: <20101012234714.GX26553@bubble.grove.modra.org> <20101013051329.GA3565@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101013051329.GA3565@gmx.de> User-Agent: Mutt/1.5.20 (2009-06-14) X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2010-10/txt/msg00286.txt.bz2 On Wed, Oct 13, 2010 at 07:13:29AM +0200, Ralf Wildenhues wrote: > > +m4_pushdef([AS_MESSAGE_LOG_FD], [])dnl > > + AC_MSG_ERROR([path to source, $srcdir, contains spaces]) > > +_m4_popdef([AS_MESSAGE_LOG_FD])dnl > > Why not m4_popdef instead of _m4_popdef? Because I cut and pasted this from somewhere else that happened to use _m4_popdef. ;-) Yes, m4_popdef works fine. -- Alan Modra Australia Development Lab, IBM