From: Andreas Ericsson <ae@op5.se>
To: Andrew Wozniak <awozniak@mc.com>
Cc: git@vger.kernel.org
Subject: Re: recent patch breaks the build ?
Date: Wed, 16 Nov 2005 21:18:06 +0100 [thread overview]
Message-ID: <437B93FE.9000108@op5.se> (raw)
In-Reply-To: <437B8CEC.8040002@mc.com>
Andrew Wozniak wrote:
> Yes, that suggestion worked - it is similar to other code fragments and
> ifdefs within the same file.
>
> Unfortunately, now there are other failures:
>
> gcc -o http-push.o -c -g -O2 -Wall -DSHA1_HEADER='<openssl/sha.h>'
> http-push.c
> http-push.c: In function `start_mkcol':
> http-push.c:479: `CURLOPT_HTTPGET' undeclared (first use in this function)
>
....
> I grep'd for these defines and they are nowhere to be found! Is some
> other package needed to resolve these undefines on my RH7.2 build host?
>
curl and curl-devel. Or you can build with
make NO_CURL=YesPlease
which just means you won't have http and https transports available.
This shouldn't be much of a problem on a server though.
> I'm really surprised that the unmodified tarball source fails to build.
> Just curious, is the git project rebuilt on a "nightly" basis to verify
> recent patches?
>
I have no idea, but since it's a developer tool in pre-1.0 I think the
general consensus is that user-friendliness in the build-process comes
somewhere between "not so important" and "what? users? oh, those living
in the *other* land!"
Perhaps you should try the RPM's at
http://www.kernel.org/pub/software/scm/git-core/ ?
If nothing else it will tell you what other packages you need.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-11-16 20:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 17:17 recent patch breaks the build ? Andrew Wozniak
2005-11-16 19:15 ` Junio C Hamano
2005-11-16 19:47 ` Andrew Wozniak
2005-11-16 20:18 ` Andreas Ericsson [this message]
2005-11-16 20:25 ` Junio C Hamano
2005-11-16 20:33 ` Nick Hengeveld
2005-11-16 23:25 ` Johannes Schindelin
2005-11-17 0:46 ` Nick Hengeveld
2005-11-17 1:15 ` Junio C Hamano
2005-11-17 2:10 ` Nick Hengeveld
2005-11-17 10:33 ` Junio C Hamano
2005-11-17 11:15 ` Johannes Schindelin
2005-11-17 12:00 ` Johannes Schindelin
2005-11-17 15:57 ` Nick Hengeveld
2005-11-17 16:22 ` Johannes Schindelin
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=437B93FE.9000108@op5.se \
--to=ae@op5.se \
--cc=awozniak@mc.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.
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).