autotools versioning, redux

Alexandre Oliva aoliva@redhat.com
Fri Feb 27 00:18:00 GMT 2004


On Feb 26, 2004, Benjamin Kosnik <bkoz@redhat.com> wrote:

>>> acinclude.m4:11: warning: underquoted definition of GLIBCXX_CONDITIONAL
>> 
>> These `underquoted definition' warnings are all bugs waiting to
>> happen.  I've alluded to the quoting rules years ago.

> Really? Hmmm. I must have missed that. So, just to make it crystal
> clear, how do these get fixed?

The general rule of thumb is, for every level of parentheses, there
should be one level of quotes.  Every argument should be quoted,
unless there's a very good reason not to do so (i.e., you're relying
on low-level m4 properties).

> AC_DEFUN(GLIBCXX_CHECK_HOST, [
           ^                ^ argument is not quoted
>   . $glibcxx_srcdir/configure.host
>   AC_MSG_NOTICE(CPU config directory is $cpu_include_dir)
                  ^                                      ^ not quoted
>   AC_MSG_NOTICE(OS config directory is $os_include_dir)
                  ^                                    ^ not quoted
> ])

>>> Makefile.am:63: user variable `MULTISRCTOP' defined here...

>> I suppose this has to do with built-in multilib support in automake.

> Ouch! So, is there a way to turn off this built-in multilib support in
> automake, or otherwise fix this?

No idea.  I just overheard people were planning on doing that; I
advised against it because we wanted to change it ourselves, to no
avail :-(

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Happy GNU Year!                     oliva@{lsd.ic.unicamp.br, gnu.org}
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist                Professional serial bug killer



More information about the Libstdc++ mailing list