From: Andrew Wozniak <awozniak@mc.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Nick Hengeveld <nickh@reactrix.com>
Subject: Re: recent patch breaks the build ?
Date: Wed, 16 Nov 2005 14:47:56 -0500 [thread overview]
Message-ID: <437B8CEC.8040002@mc.com> (raw)
In-Reply-To: <7v64qs8kuo.fsf@assigned-by-dhcp.cox.net>
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)
http-push.c:479: (Each undeclared identifier is reported only once
http-push.c:479: for each function it appears in.)
http-push.c: In function `start_move':
http-push.c:581: `CURLOPT_HTTPGET' undeclared (first use in this function)
http-push.c: In function `refresh_lock':
http-push.c:615: `CURLOPT_HTTPGET' undeclared (first use in this function)
http-push.c: In function `fetch_index':
http-push.c:890: `CURLOPT_HTTPGET' undeclared (first use in this function)
http-push.c: In function `lock_remote':
http-push.c:1215: `CURLOPT_HTTPGET' undeclared (first use in this function)
http-push.c: In function `main':
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?
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?
Thanks again, Andrew
Junio C Hamano wrote:
> Andrew Wozniak <awozniak@mc.com> writes:
>
>> Have just started using git for u-boot related development. After
>> downloading git-snapshot-20051116 tarball and attempting a build under
>> RH7.2, I get the following failure:
>
> Would this help?
>
> -- >8 --
>
> diff --git a/http-fetch.c b/http-fetch.c
> index 21cc1b9..45e97f9 100644
> --- a/http-fetch.c
> +++ b/http-fetch.c
> @@ -902,16 +902,18 @@ static void fetch_alternates(char *base)
> char *data;
> struct active_request_slot *slot;
> static struct alt_request alt_req;
> - int num_transfers;
>
> +#ifdef USE_CURL_MULTI
> /* If another request has already started fetching alternates,
> wait for them to arrive and return to processing this request's
> curl message */
> while (got_alternates == 0) {
> + int num_transfers;
> curl_multi_perform(curlm, &num_transfers);
> process_curl_messages();
> process_request_queue();
> }
> +#endif
>
> /* Nothing to do if they've already been fetched */
> if (got_alternates == 1)
>
>
next prev parent reply other threads:[~2005-11-16 19:48 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 [this message]
2005-11-16 20:18 ` Andreas Ericsson
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=437B8CEC.8040002@mc.com \
--to=awozniak@mc.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nickh@reactrix.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).