bug-autoconf
[Top][All Lists]
Advanced

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

BUG-Report


From: Jens Krüger
Subject: BUG-Report
Date: Thu, 15 Feb 2001 08:11:41 +0100

I tried to make latest autoconf from CVS (from 02/14/01) and got the following
message from configure:

./configure --prefix=/usr

checking for a BSD compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for expr... /usr/bin/expr
checking for gm4... no
checking for gnum4... no
checking for m4... /usr/bin/m4
checking whether m4 supports frozen files... yes
checking for mawk... no
checking for gawk... gawk
checking for working help2man... missing
checking for perl... /usr/bin/perl
checking for a BSD compatible install... /usr/bin/ginstall -c
configure: creating ./config.status
config.status: creating Makefile
config.status: creating m4/Makefile
config.status: creating man/Makefile
config.status: creating doc/Makefile
config.status: creating tests/Makefile
config.status: creating tests/atconfig
* 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.
 -- 
Jens Krüger
Tel: + 49 89 289 14 716
mailto:address@hidden
http://www.physik.tu-muenchen.de

Attachment: testsuite.log
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]