Arvind Sankar 5ca349f95d Fix check for sed --in-place ... The test added in commit 4313a5b4c5 ("Detect if sed supports --in-place") doesn't work at least on my system (autoconfig-2.69). The issue is that SED has already been found and cached before this function is evaluated, with the result that the test is completely skipped. ... checking for a sed that does not truncate output... /usr/bin/sed ... checking for sed --in-place... (cached) /usr/bin/sed The first test is executed by libtool.m4. This looks to have been around in libtool for at least 15 years or so, not sure why this was not encountered at the time of the original commit. Fix this by caching the value of the ac_inplace flag rather than the path to SED. Also use $SED and add AC_REQUIRE to ensure that we use the sed that was located by the standard configure test. Reviewed-by: Ryan Moeller <ryan@iXsystems.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Arvind Sankar <nivedita@alum.mit.edu> Closes #10493		2020-06-24 18:19:59 -07:00
..
bin	Fix check for sed --in-place	2020-06-24 18:19:59 -07:00
include	Exit status 256+signum is actually baked in to ksh	2020-03-17 09:49:58 -07:00
man	ZTS: Add a failsafe callback to run after each test	2020-03-10 11:00:56 -07:00
Makefile.am	Retire legacy test infrastructure	2017-08-15 17:26:38 -07:00