Update of sr #110283 (project autoconf):
Status: Ready For Test => Done
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #5:
The patch I posted here earlier was necessary but not sufficient to fix all
the spurious testsuite failures due to _AST_FEATURES. I have now pushed a
complete fix.
As of revision 2cb0ab81, I get a completely successful testsuite on weerd with
all three of these $PATH settings:
- /usr/gnu/bin:/usr/bin:/usr/sbin:/sbin
- /usr/bin:/usr/sbin:/sbin
- /usr/xpg4/bin:/usr/bin:/usr/sbin:/usr/sbin
In the latter two cases I used "gmake check" instead of "make check" because
of #110289 -- further discussion of that problem should happen in that
ticket.
With /usr/xpg4/bin first in the path, I needed to set
ACCEPT_INFERIOR_RM_PROGRAM=yes in the environment before running 'configure',
but having done that, there were no additional problems. Any change to the
behavior of AM_INIT_AUTOMAKE needs to happen in automake first, and the
workaround of setting this environment variable is suggested in the error
message that prints when 'rm -f' with no arguments exits unsuccessfully, so I
don't think we need to make any additional changes on our side, yet.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110283>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
