[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[sr #110289] "/bin/sh: line 1: ../tests/mktests.sh: not found" with dmak
From: |
Paul Eggert |
Subject: |
[sr #110289] "/bin/sh: line 1: ../tests/mktests.sh: not found" with dmake and separate build dir |
Date: |
Tue, 4 Aug 2020 19:32:19 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0 |
Follow-up Comment #1, sr #110289 (project autoconf):
The usual fix for this sort of problem is to not use 'cd'. Does that work?
That is, can you replace the offending shell command with:
$(SHELL) $(srcdir)/tests/mktests.sh \
`echo " "$(AUTOCONF_FILES) | sed 's, [^ ]*/,
$(srcdir)/lib/autoconf/,g'`
Anyway, as I understand it, this problem should not occur when building with a
distribution tarball because such a tarball already contains an up-to-date
mktests.stamp. So the problem should occur only when building from Git, or
when someone has changed one of mktests.stamp's dependencies and is developing
Autoconf rather than just building it.
If the problem is limited to Solaris dmake and doesn't occur with GNU make,
it's a low-priority bug - we can just tell people to use a GNU-compatible
'make' if they want to develop (as opposed to merely build) Autoconf. This
would be a reasonable approach to take if the abovementioned trivial patch
does not work.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110289>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/