[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: macro name as literal string?
From: |
Daniel Jacobowitz |
Subject: |
Re: macro name as literal string? |
Date: |
Fri, 12 Dec 2003 16:37:30 -0500 |
User-agent: |
Mutt/1.5.1i |
On Fri, Dec 12, 2003 at 03:37:05PM -0500, Eric Sunshine wrote:
> On Fri, 12 Dec 2003 15:02:04 -0500, Bob Lockie wrote:
> > On 12/12/03 04:58 Andreas Schwab spoke thusly<br>
> > > Bob Lockie <address@hidden> writes:
> > >>I want to have the following but having the text AH_TEMPLATE is picked up
> > >>by autoheader and a blank #undef is created.
> > >>AC_CHECK_FILE( [acconfig.h], AC_MSG_ERROR( [the config template is
> > >>created by the AH_TEMPLATE commands in configure.in|ac so delete
> > >>acconfig.h] ), )
> > > Try enclosing the second argument of AC_CHECK_FILE in []. Underquoted
> > > arguments are the topmost source of errors.
> > Like that?
> > AC_CHECK_FILE( [acconfig.h], [AC_MSG_ERROR( [the config template is
> > created by the AH_TEMPLATE commands in configure.in|ac so delete
> > acconfig.h] )], )
> > It didn't work.
>
> You can also prevent m4 from recognizing macros by inserting arbitrary
> quotes into the names. For instance AH_TEM[]PLATE or AH_T[EMP]LATE.
I believe the currently preferred way to do this is AH@&address@hidden
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer