git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Wozniak <awozniak@mc.com>
To: git@vger.kernel.org
Subject: recent patch breaks the build ?
Date: Wed, 16 Nov 2005 12:17:11 -0500	[thread overview]
Message-ID: <437B6997.8010903@mc.com> (raw)

Hello,

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:

gcc -o http-fetch.o -c -g -O2 -Wall -DSHA1_HEADER='<openssl/sha.h>' 
http-fetch.c
http-fetch.c: In function `fetch_alternates':
http-fetch.c:911: warning: implicit declaration of function 
`curl_multi_perform'
http-fetch.c:911: `curlm' undeclared (first use in this function)
<snip>

It appears that a recent patch "Fix for multiple alternates requests in 
http" references curlm without the necessary #ifdef USE_CURL_MULTI

I'm not that familiar with the git architecture and codebase, so any 
suggestions for a workaround are much appreciated.

Thank you

             reply	other threads:[~2005-11-16 17:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 17:17 Andrew Wozniak [this message]
2005-11-16 19:15 ` recent patch breaks the build ? Junio C Hamano
2005-11-16 19:47   ` Andrew Wozniak
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=437B6997.8010903@mc.com \
    --to=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).