configure.ac: fix HAVE_SYNC_FILE_RANGE definition

me-and · gitster · commit 2e3759479715 · 2022-04-06T09:36:19.000-07:00
If sync_file_range is not available when building the configure script,
there is a cosmetic bug when running that script reporting
"HAVE_SYNC_FILE_RANGE: command not found".  Remove that error message by
defining HAVE_SYNC_FILE_RANGE to an empty string, rather than generating
a script where that appears as a bare command.

Signed-off-by: Adam Dinwoodie &lt;adam@dinwoodie.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
diff --git a/configure.ac b/configure.ac
@@ -1087,7 +1087,7 @@ GIT_CONF_SUBST([HAVE_CLOCK_MONOTONIC])
 # Define HAVE_SYNC_FILE_RANGE=YesPlease if sync_file_range is available.
 GIT_CHECK_FUNC(sync_file_range,
 	[HAVE_SYNC_FILE_RANGE=YesPlease],
-	[HAVE_SYNC_FILE_RANGE])
+	[HAVE_SYNC_FILE_RANGE=])
 GIT_CONF_SUBST([HAVE_SYNC_FILE_RANGE])
 
 #

Original file line number	Diff line number	Diff line change
`@@ -1087,7 +1087,7 @@ GIT_CONF_SUBST([HAVE_CLOCK_MONOTONIC])`
`1087`	`1087`	`# Define HAVE_SYNC_FILE_RANGE=YesPlease if sync_file_range is available.`
`1088`	`1088`	`GIT_CHECK_FUNC(sync_file_range,`
`1089`	`1089`	`[HAVE_SYNC_FILE_RANGE=YesPlease],`
`1090`		`- [HAVE_SYNC_FILE_RANGE])`
	`1090`	`+ [HAVE_SYNC_FILE_RANGE=])`
`1091`	`1091`	`GIT_CONF_SUBST([HAVE_SYNC_FILE_RANGE])`
`1092`	`1092`
`1093`	`1093`	`#`