git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: How to force configure script to use curl ?
Date: Fri, 14 Feb 2020 11:49:25 -0500	[thread overview]
Message-ID: <EF7D86BC-9EF7-4333-A786-2EC7DCF72C74@gmail.com> (raw)
In-Reply-To: <20200214061714.GA605125@coredump.intra.peff.net>

Hi Peff,

Thanks for a very sensible suggestion!

Philippe. 

> Le 14 févr. 2020 à 01:17, Jeff King <peff@peff.net> a écrit :
> 
>> On Wed, Feb 12, 2020 at 05:08:06PM -0500, Philippe Blain wrote:
>> 
>> 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?)
> 
> I don't think so. It would probably be possible for configure.ac to
> behave this way. Looking at the code, I think GIT_PARSE_WITH would have
> to record the affirmative for "--with" instead of just canceling a
> previous "--without", and then the part that does curl auto-detection
> would need to complain if it doesn't find curl at that point.
> 
> But our use of autoconf is not very extensive, and in fact most
> developers do not use it at all. If you know you want curl, you're
> better off just overriding it explicitly with the Makefile knob:
> 
>  make NO_CURL=
> 
> or:
> 
>  echo NO_CURL= >>config.mak
>  make
> 
> Either of those will override the NO_CURL setting done by the configure
> script (you can see the full list of knobs set by configure in
> config.mak.autogen).
> 
> -Peff

      parent reply	other threads:[~2020-02-14 16:49 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
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 [this message]

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=EF7D86BC-9EF7-4333-A786-2EC7DCF72C74@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).