From: "Torsten Bögershausen" <tboegi@web.de>
To: Divyansh Garg <divyansh.gargsg@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GSOC] fatal error: curl/curl.h: No such file or directory
Date: Sat, 20 Feb 2021 15:11:03 +0100 [thread overview]
Message-ID: <20210220141102.t43mb4gxwzseides@tb-raspi4> (raw)
In-Reply-To: <CAB=huCZLwkBv-Fd4iUqbDwNuNfeFBfjPfKRzYUGShc727KJJzg@mail.gmail.com>
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.
Welcome to the Git community.
You need to install the development package of some packages,
which come with header files (and not only the libs).
Being a lazy person, I collected all possible package names in a setupscript,
looking similar to this:
APTGET="sudo apt-get install"
type curl-config || $APTGET libcurl4-openssl-dev || $APTGET libcurl-devel
test -r /usr/include/expat.h || $APTGET libexpat1-dev || $APTGET expat-devel || $APTGET libexpat-devel
test -r /usr/include/ssl.h || test -r /usr/include/openssl/ssl.h || $APTGET openssl-devel || $APTGET libssl-dev
test -r /usr/include/zlib.h || $APTGET zlib1g-dev
type msgfmt || $APTGET gettext
In other words,
sudo apt-get install libcurl-devel
could help.
And you probably need to install more dev/devel packages, unfortunatly different Linux distros
use different names for (from a user point of view) the same thing.
So I can't tell you out of my head, what Ubuntu needs, but there is hopefully a start point.
[snip]
next prev parent reply other threads:[~2021-02-20 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 13:57 [GSOC] fatal error: curl/curl.h: No such file or directory Divyansh Garg
2021-02-20 14:11 ` Torsten Bögershausen [this message]
2021-02-20 19:07 ` SZEDER Gábor
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=20210220141102.t43mb4gxwzseides@tb-raspi4 \
--to=tboegi@web.de \
--cc=divyansh.gargsg@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).