Update of sr #110740 (project autoconf):
Priority: 3 - Low => 5 - Normal
Severity: 2 - Minor => 3 - Normal
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #6:
Thanks for mentioning the postgresql situation. I went back and looked back at
autoconf, and it seems to me that all things considered,nowadays the cure of
using a relative install-sh path is worse than the disease of ancient mkdirs
that don't work properly. If so, it's better now for AC_PROG_MKDIR_P to fall
back on plain mkdir -p than on a relative path to install-sh, so I installed a
patch to do that
<https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=d081ac3ec80d551c3fdd3d74ade368acce3fc4a8>.
Only the last four lines of that patch affect functionality; everything else
is documentation.
Assuming postgresql wants to work with current Autoconf, it can put in
something like "case $MKDIR_P in /*) ;; */*) MKDIR_P='mkdir -p';; esac" into
the appropriate place in configure.ac. This should work around the problem
now, and should be a no-op in later Autoconf versions.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110740>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
