Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: felix-git@fefe.de
Cc: git@vger.kernel.org
Subject: Re: git completely non-operational w/ curl 7.16.0
Date: Wed, 03 Jan 2007 22:45:54 -0800	[thread overview]
Message-ID: <7vvejnmgrh.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070104023150.GA31151@codeblau.de> (felix-git@fefe.de's message of "Thu, 4 Jan 2007 03:31:51 +0100")

felix-git@fefe.de writes:

> I'm using git 1.4.4.3 on x86_64-linux with curl 7.16.0, glibc 2.5, gcc
> 4.1.1 and binutils 2.17.  All of these are as far as I know the current
> release versions.

This may be related to a bug in cURL 7.16.0, which is reported
to be fixed in their current CVS version:

	http://curl.haxx.se/mail/archive-2006-12/0085.html

In the meantime, we have a workaround for this particular
problem the above URL mentions since last week.

Please try "master" (or anything later than v1.5.0-rc0) to see
if it still breaks for you.

The fix also should apply cleanly on top of 1.4.4.3.

-- >8 --
[PATCH] Work around http-fetch built with cURL 7.16.0

It appears that curl_easy_duphandle() from libcurl 7.16.0
returns a curl session handle which fails GOOD_MULTI_HANDLE()
check in curl_multi_add_handle().  This causes fetch_ref() to
fail because start_active_slot() cannot start the request.

For now, check for 7.16.0 to work this issue around.

Signed-off-by: Junio C Hamano <junkio@cox.net>

diff --git a/http.h b/http.h
index 6e12e41..324fcf4 100644
--- a/http.h
+++ b/http.h
@@ -18,7 +18,7 @@
 #define curl_global_init(a) do { /* nothing */ } while(0)
 #endif
 
-#if LIBCURL_VERSION_NUM < 0x070c04
+#if (LIBCURL_VERSION_NUM < 0x070c04) || (LIBCURL_VERSION_NUM == 0x071000)
 #define NO_CURL_EASY_DUPHANDLE
 #endif
 

      reply	other threads:[~2007-01-04  6:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04  2:31 git completely non-operational w/ curl 7.16.0 felix-git
2007-01-04  6:45 ` Junio C Hamano [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

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

  git send-email \
    --in-reply-to=7vvejnmgrh.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=felix-git@fefe.de \
    --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