1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
-*- outline -*-
This file lists the bugs you must be aware of. Be sure to check this
file before using Autoconf, and especially CVS versions of Autoconf.
Autoconf must not be used in production if there are ``Serious'' bugs,
and use with caution an Autoconf with ``Important bugs''.
Many other bugs are registered on the GNATS server:
http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=autoconf
Please, don't register bugs listed below: we already know we have to
address them.
* Status
/*-------------.
| Do not use. |
`-------------*/
* Serious Problems
** Broken compilers
configure does not properly diagnose broken compilers (because it
finds the failure before the code that checks whether the compiler
works). It is not to serious a bug, but most notably the test suite
will fail to handle gracefully missing compilers (typically the
Fortran compiler).
** 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
and all the macros that use it, are paying the change for test -f to
test -x to determine whether a candidate path is an executable: now we
have false positives with directories which, indeed, are test -x.
|
