From: Christian Couder <christian.couder@gmail.com>
To: Philippe Blain <levraiphilippeblain@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: How to force configure script to use curl ?
Date: Thu, 13 Feb 2020 11:07:28 +0100 [thread overview]
Message-ID: <CAP8UFD3Xi_56qqiDstquHZ9i=RDF_ka7NJMniiw5cvcrV90oLA@mail.gmail.com> (raw)
In-Reply-To: <A0910AA2-D24B-4DF5-8D39-8E2D8B56955B@gmail.com>
Hi,
On Wed, Feb 12, 2020 at 11:09 PM Philippe Blain
<levraiphilippeblain@gmail.com> wrote:
> I was trying to build Git yesterday on a Ubuntu 14 machine that was missing the package "libcurl4-gnutls-dev" necessary to build the http(s) remote helper [1].
>
> Doing just
>
> ./configure
> make
>
> built Git without support for the http remote helper, as expected.
>
> However, doing
>
> ./configure --with-curl
> make
>
> did the same; it did not result in an error saying that the curl headers could not be found (which I expected).
>
> Is there a way to force the configure script to error out if it does not find curl (or any one of the optional dependencies that I happen to need for my build?)
Using the configure script is not needed. Building Git using just a
make command can work.
You might want to try it and see if it fails as you expect when
libcurl4-gnutls-dev is not installed.
In the top level Makefile you can see all the variables that can be
set to customize the build.
These days the configure infrastructure is not as well maintained as
the Makefile.
Best,
Christian.
next prev parent reply other threads:[~2020-02-13 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 22:08 How to force configure script to use curl ? Philippe Blain
2020-02-13 10:07 ` Christian Couder [this message]
2020-02-14 6:17 ` Jeff King
2020-02-14 16:31 ` Junio C Hamano
2020-02-14 16:43 ` Jeff King
2020-02-14 16:49 ` Philippe Blain
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD3Xi_56qqiDstquHZ9i=RDF_ka7NJMniiw5cvcrV90oLA@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=levraiphilippeblain@gmail.com \
/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.
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 NNTP newsgroup(s).