Re: autoconf for type sizes

[Akim Demaille <akim at epita dot fr>]

| The last time I gave it a try (actually, I used to try to build CVS
| autotools on day-o-day basis)
| merlin% /codesourcery/autoconf/configure
| [...] 
| 
|     * Status
| 
|             /*-------------.
|             | Do not use.  |
|             `-------------*/
| 
|     * Serious Problems
| 
|     ** Special characters and config.hin
| 
|     The handling of special characters, most notable backslashes, of
|     course, might be nonportable in addition of being of clearly
|     specified.
| 
|     ** AC_TRY_EVAL of multi line commands
| 
|     Is broken.  The problem is mostly that, again, the policy wrt special
|     characters is not clearly defined.  Because of this,
|     _AC_INIT_PREPARE_FS_SEPARATORS will output undesired messages, but is
|     not guilty.
| 
|     ./configure: /home/lrde/prof/akim/src/ace/tests; conftest.sh: Aucun
|     fichier ou r
|             pertoire de ce type
| 
|     AC_TRY_COMMAND is.
| 
|     ** AC_CHECK_PROG
| 
| That is, even a plain ./configure to prepare installation failed.

No, read better.  configure gave you some information about the status
of the Autoconf you downloaded.  I see no errors in there.  And of
course, I'm not suggesting that you use versions that I stamped as `Do
not use.'.

| Before asking GGC folks so switch to CVS autotools, those tools need
| to be minimaly reliable.

Agreed, that's why I'm talking about 2.49d, and that's why I said
2.49c was not to be used.  But we learned it thanks to people who gave
it a try.