[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Test log
From: |
Zack Weinberg |
Subject: |
Re: Test log |
Date: |
Fri, 16 Sep 2022 10:24:57 -0400 |
User-agent: |
Cyrus-JMAP/3.7.0-alpha0-935-ge4ccd4c47b-fm-20220914.001-ge4ccd4c4 |
On Fri, Sep 16, 2022, at 8:41 AM, Malte Lindestam wrote:
> I'm trying to install autoconf and was instructed to send this.
>
> I'm on a macbook pro, m1 pro. I don't really know what I'm doing :(
The first concrete failure in the log file is due to this error:
+/Users/malteli/Code
installs/autoconf-2.71/tests/testsuite.dir/at-groups/227/test-source: line 150:
/Users/malteli/Code: No such file or directory
This is a known, long-standing limitation in all three of Autoconf, Automake,
and GNU make. The absolute pathname of the source directory needs to not
contain any spaces or other special characters.
Some of the other failures are probably due to the same issue, and others are
due to a bug that has been fixed in the development sources. We should
probably put out a 2.72 but I doubt I will have time to do that until December
(and there are some other changes that we ought to get in).
I recommend that you do the following:
- Rename your "Code installs" directory to "Code-installs" or something like
that.
- Rebuild autoconf 2.71 from scratch.
- You _should_ then see only these testsuite failures:
509. acheaders.at:9: 509. AC_CHECK_HEADER_STDBOOL (acheaders.at:9): FAILED
(acheaders.at:9)
514. acheaders.at:14: 514. AC_HEADER_STDBOOL (acheaders.at:14): FAILED
(acheaders.at:14)
These are due to the bug I mentioned. It is a relatively minor bug and you can
probably just live with it.
zw
- Test log, Malte Lindestam, 2022/09/16
- Re: Test log,
Zack Weinberg <=