list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: "SZEDER Gábor" <>
To: Divyansh Garg <>
Subject: Re: [GSOC] fatal error: curl/curl.h: No such file or directory
Date: Sat, 20 Feb 2021 20:07:28 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Feb 20, 2021 at 07:27:32PM +0530, Divyansh Garg wrote:
> Hello,
> I am trying to build the source code on my system (Ubuntu 20.04).
> After cloning the repo, when I proceed with the command: make, I get
> the following error.
> I tried installing curl and searched the internet but couldn't get a fix.
> Please advise, how can I solve this problem.
> divyansh:~/gsoc/git$ make
> make: curl-config: Command not found
>     * new prefix flags
>     CC attr.o
>     CC config.o
>     CC exec-cmd.o
>     CC gettext.o
>     AR libgit.a
>     LINK git-daemon
>     LINK git-http-backend
>     LINK git-imap-send
>     LINK git-sh-i18n--envsubst
>     LINK git-shell
>     CC http.o
> In file included from http.c:2:
> http.h:6:10: fatal error: curl/curl.h: No such file or directory
>     6 | #include <curl/curl.h>
>       |          ^~~~~~~~~~~~~
> compilation terminated.
> make: *** [Makefile:2422: http.o] Error 1

As Torsten said you have to install not only a couple of libraries but
also the related '-dev' package containing includes and static

In our CI jobs using Ubuntu we install the following packages by
default (see 'ci/'):

UBUNTU_COMMON_PKGS="make libssl-dev libcurl4-openssl-dev libexpat-dev
 tcl tk gettext zlib1g-dev perl-modules liberror-perl libauthen-sasl-perl
 libemail-valid-perl libio-socket-ssl-perl libnet-smtp-ssl-perl"

      parent reply	other threads:[~2021-02-20 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 13:57 Divyansh Garg
2021-02-20 14:11 ` Torsten Bögershausen
2021-02-20 19:07 ` SZEDER Gábor [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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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 inbox:

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).