Re: wacky warning in 2.68...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Miles Bader <miles@xxxxxxx> writes:
> Russ Allbery <rra@xxxxxxxxxxxx> writes:

>> You're missing a level of quoting.  That should be:
>>     AC_COMPILE_IFELSE([AC_LANG_SOURCE([int x;])], [opt_ok=yes], [opt_ok=no])

> Hmm, ok.

> [I'm not sure if I'm _ever_ going to really have any intuitive sense for
> quoting in autoconf....]

This one was a little weird, and the only reason why I know it off the top
of my head is that it's been a frequent report.  I think there was an
explanation on the list a while back about how that error message pops out
of the internals with that problem.

But in general you're not going to go wrong by just single-quoting every
argument of every Autoconf macro always.  Once I started doing that, most
of these odd problems went away, since the legacy stuff that didn't work
properly with quoting is mostly gone now.  The only exception is that
sometimes I double-quote with [[ ]] for literal text with [] in it.  Once
in a blue moon there's some sort of bug with overquoting.  But nearly all
the weird problems people run into with Autoconf understanding its input
are from underquoting some macro argument somewhere.

-- 
Russ Allbery (rra@xxxxxxxxxxxx)             <http://www.eyrie.org/~eagle/>

_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://lists.gnu.org/mailman/listinfo/autoconf


[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux