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

--with-curl vs --with-curl-path=PATH

From
JWJeffrey Walton <noloader@gmail.com>
Date
Mar 9, 2019, 11:35 UTC
Message-ID
<CAH8yC8nMe-LmmS+KvBDATWu-C-FZef2PbT1FpHECGb_paeyYMA@mail.gmail.com>

I'm trying to build Git and install it in a discardable directory. All of Git's prereqs have been built and are there.

Git was configured with --with-curl, but it looks like Git cannot find the cURL built for it (see below). I tried adding -lcurl to LDLIBS but it does not appear to be honored. cURL is also available from PKG_CONFIG_PATH, but it does not appear it is being used:

$ PKG_CONFIG_PATH=/var/sanitize/lib64/pkgconfig pkg-config --print-provides libcurl libcurl = 7.64.0

My question is, how can I get the behavior of --with-curl-path=<custom path>? At the moment the only option offered is --with-curl.

$ make V=1
...
make: curl-config: Command not found
...
gcc -I/var/sanitize/include -DNDEBUG -g2 -O2 -fsanitize=undefined
-march=native -fPIC -I. -DHAVE_SYSINFO -DGIT_HOST_CPU="\"x86_64\""
-DUSE_LIBPCRE2 -I/var/sanitize/include -DHAVE_ALLOCA_H
-I/var/sanitize/include -I/var/sanitize/include
-I/var/sanitize/include -I/var/sanitize/include -DSHA1_DC
-DSHA1DC_NO_STANDARD_INCLUDES -DSHA1DC_INIT_SAFE_HASH_DEFAULT=0
-DSHA1DC_CUSTOM_INCLUDE_SHA1_C="\"cache.h\""
-DSHA1DC_CUSTOM_INCLUDE_UBC_CHECK_C="\"git-compat-util.h\""
-DSHA256_BLK  -DHAVE_PATHS_H -DHAVE_LIBCHARSET_H -DHAVE_STRINGS_H
-DHAVE_DEV_TTY -DHAVE_CLOCK_GETTIME -DHAVE_CLOCK_MONOTONIC
-DHAVE_GETDELIM '-DPROCFS_EXECUTABLE_PATH="/proc/self/exe"'
-DFREAD_READS_DIRECTORIES -DNO_STRLCPY -DSHELL_PATH='"/bin/sh"'
-DPAGER_ENV='"LESS=FRX LV=-c"' -o git-http-fetch -L/var/sanitize/lib64
-fsanitize=undefined -Wl,-R,/var/sanitize/lib64 -Wl,--enable-new-dtags
 http.o http-walker.o http-fetch.o common-main.o \
        -L/var/sanitize/lib64 -Wl,-rpath,/var/sanitize/lib64  libgit.a
xdiff/lib.a  -lpcre2-8 -L/var/sanitize/lib64
-Wl,-rpath,/var/sanitize/lib64 -L/var/sanitize/lib64
-Wl,-rpath,/var/sanitize/lib64 -lz -L/var/sanitize/lib64
-Wl,-rpath,/var/sanitize/lib64 -liconv  -lcharset -lrt -lpthread
/bin/ld: http.o: in function `http_opt_request_remainder':
/home/test/git-2.21.0/http.c:1833: undefined reference to `curl_easy_setopt'
/bin/ld: http.o: in function `process_curl_messages':
/home/test/git-2.21.0/http.c:261: undefined reference to `curl_multi_info_read'
...
Message 1 of 1 in “--with-curl vs --with-curl-path=PATH”
  1. Jeffrey WaltonMar 9, 2019

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.