autotools versioning, redux
Phil Edwards
phil@jaj.com
Thu Feb 26 19:03:00 GMT 2004
On Thu, Feb 26, 2004 at 11:46:53AM -0600, Benjamin Kosnik 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? Here's one that warns:
>
> acinclude.m4:AC_DEFUN(GLIBCXX_CHECK_HOST
We need to be doing AC_DEFUN([GLIBCXX_CHECK_HOST], [ .... ]) instead.
I'd started investigating going to then-current autotools, and found some
of these errors. Bugs in the then-current release of automake stopped me
from going any further. Those are fixed in CVS automake/aclocal, but I
hadn't seen them do another release.
The way aclocal finds ac_include'd files is obscurely different in newer
tools (this was also where the bug was). We're probably going to have
to start passing command-line options to the tools when reconfiguring,
which makes me think that for the sake of developer sanity, we should
recommend this procedure for making configury changes:
1) build an unmodified tree with --enable-maintainer-mode
2) make the changes
3) let 'make' handle the various regenerations, including option passing
Also/Alternatively, the regeneration sequence can be stuffed into a very
small shell script sitting wherever.
> >> Makefile.am:63: user variable `MULTISRCTOP' defined here...
> >
> >I suppose this has to do with built-in multilib support in automake.
Huh, that's a new one to me. I will look into this.
Phil
--
The two key words tonight are "caution" and "flammable".
- Elvis, _Bubba Ho-Tep_
More information about the Libstdc++
mailing list