All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Paul Walker <PWalker752@aol.com>
Cc: git@vger.kernel.org
Subject: Re: installation issue when building with NO_CURL=YesPlease
Date: Wed, 26 May 2010 15:58:39 +0200	[thread overview]
Message-ID: <AANLkTimsGdv-La_poLpdrvuGChD6_sAD77fcjqKn5PAd@mail.gmail.com> (raw)
In-Reply-To: <5B1E2CF0-4BC4-43FF-A372-EB3582DA6286@aol.com>

Hi,

> As I could not find any bug reporting information on the wiki I thought I
> would mention this here, please let me know if there is a better forum for
> bug reports.

Bugs are usually reported on this mailing list.

> I believe the latest git release (1.7.1.) has an installation
> bug when building with "NO_CURL=YesPlease".  Looking at the Makefile line
> 1999 it reads
>
> for p in $(REMOTE_CURL_ALIASES); do
>
> which results in "/bin/sh: syntax error at line 1 : `;' unexpected" as
> REMOTE_CURL_ALIASES is empty.

I can't reproduce this. How exactly are you building? I'm using
$ NO_CURL=YesPlease make
... and it builds fine for me.

-- Ram

  parent reply	other threads:[~2010-05-26 13:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 13:35 installation issue when building with NO_CURL=YesPlease Paul Walker
2010-05-26 13:58 ` Michael J Gruber
2010-05-26 14:41   ` Paul Walker
2010-05-26 13:58 ` Ramkumar Ramachandra [this message]
2010-05-26 14:15   ` Paul Walker
2010-05-26 14:24     ` [PATCH] Makefile: reenable install with NO_CURL Michael J Gruber
2010-05-26 18:27     ` installation issue when building with NO_CURL=YesPlease Dirk Süsserott
2010-05-26 18:45       ` Bruce Stephens
2010-05-26 19:03         ` Dirk Süsserott
2010-07-02 18:50         ` [PATCH 1/2] Makefile: remove some unnecessary curly braces Brandon Casey
2010-07-02 18:50         ` [PATCH 2/2] Makefile: work around ksh's failure to handle missing list argument to for loop Brandon Casey
2010-07-03  6:21           ` Raja R Harinath
2010-07-04 18:37           ` Michael J Gruber
2010-07-05  6:19             ` Johannes Sixt
2010-07-05  8:14               ` Michael J Gruber
2010-07-05  9:15                 ` Johannes Sixt
2010-07-05  9:31                   ` Michael J Gruber
2010-07-05 18:18               ` Junio C Hamano
2010-07-05 20:00                 ` Andreas Schwab
2010-07-05 21:29                 ` Brandon Casey
2010-07-06  2:36                   ` Junio C Hamano
2010-07-06 21:56                     ` [PATCH 2/2 v2] " Brandon Casey

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=AANLkTimsGdv-La_poLpdrvuGChD6_sAD77fcjqKn5PAd@mail.gmail.com \
    --to=artagnon@gmail.com \
    --cc=PWalker752@aol.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.