git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] configure.ac: fix HAVE_SYNC_FILE_RANGE definition

From
Adam Dinwoodie <adam@dinwoodie.org>
Date
Apr 5, 2022, 10:00 UTC
Message-ID
<20220405100020.48663-1-adam@dinwoodie.org>

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 <adam@dinwoodie.org>
---
 configure.ac | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index 6bd6bef1c4..316a31d231 100644
--- 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])
 
 #
-- 
2.35.1
Next: Neeraj Singh
Message 1 of 3 in “configure.ac: fix HAVE_SYNC_FILE_RANGE definition”
  1. configure.ac: fix HAVE_SYNC_FILE_RANGE definitionAdam Dinwoodie, Apr 5, 2022
  2. Neeraj SinghApr 5, 2022
  3. Junio C HamanoApr 6, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.