From: Jeffrey Walton <noloader@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: --with-curl vs --with-curl-path=PATH
Date: Sat, 9 Mar 2019 06:35:58 -0500 [thread overview]
Message-ID: <CAH8yC8nMe-LmmS+KvBDATWu-C-FZef2PbT1FpHECGb_paeyYMA@mail.gmail.com> (raw)
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'
...
reply other threads:[~2019-03-09 11:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH8yC8nMe-LmmS+KvBDATWu-C-FZef2PbT1FpHECGb_paeyYMA@mail.gmail.com \
--to=noloader@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).