All of lore.kernel.org
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>
Subject: Re: GIT on MinGW problem
Date: Sun, 27 May 2007 04:02:22 -0300	[thread overview]
Message-ID: <46592CFE.40303@xs4all.nl> (raw)
In-Reply-To: <20070527063902.GB28023@spearce.org>

Shawn O. Pearce escreveu:
> 
> On systems like Cygwin the fork+exec overheads are very high;
> running a "simple" configure script can take longer than it
> takes me to compile Git from scratch.  Editing config.mak is
> quite easy; so is passing your choices on the command line to
> `make install`.
> 
> Personally I find:
> 
> 	make NO_CURL=1 install
> 
> easier than:
> 
> 	./configure --without-curl && make install

NO_CURL is a nonstandard option. Every package does it
differently, so this requires users to delve through either
INSTALL or Makefile. 

A well written configure script is able to detect presence
of a linkable libcurl. 

-- 
 Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

  reply	other threads:[~2007-05-27  7:05 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12  1:13 GIT on MinGW problem Aaron Gray
2007-05-12  1:17 ` Junio C Hamano
2007-05-12  2:25   ` Aaron Gray
2007-05-12  3:30 ` Han-Wen Nienhuys
2007-05-25  8:49   ` Johannes Sixt
2007-05-25  9:45     ` Marco Costalba
2007-05-25 10:20     ` Johannes Schindelin
2007-05-25 11:07       ` Johannes Sixt
2007-05-26 19:42       ` Han-Wen Nienhuys
2007-05-26 22:17         ` Johannes Schindelin
2007-05-27  6:56           ` Han-Wen Nienhuys
2007-05-27 10:52             ` Johannes Schindelin
2007-05-27 17:04               ` Han-Wen Nienhuys
2007-05-28 16:54                 ` Nix
2007-05-27 20:44           ` Han-Wen Nienhuys
     [not found]             ` <Pine.LNX.4.64.0705272213350.4648@racer.site>
     [not found]               ` <f329bf540705271417k1874c1f2u3acc98dc25e058b9@mail.gmail.com>
2007-05-27 21:26                 ` Johannes Schindelin
2007-05-25 21:37     ` Aaron Gray
2007-05-26 19:41     ` Han-Wen Nienhuys
2007-05-26 22:26       ` Johannes Schindelin
2007-05-26 22:39         ` Junio C Hamano
2007-05-26 22:45           ` Johannes Schindelin
2007-05-26 22:53         ` Han-Wen Nienhuys
2007-05-26 23:47           ` Jakub Narebski
2007-05-27  6:30             ` Han-Wen Nienhuys
2007-05-27  6:39               ` Shawn O. Pearce
2007-05-27  7:02                 ` Han-Wen Nienhuys [this message]
2007-05-27  7:21                   ` Steven Grimm
2007-05-27  9:09                     ` Jakub Narebski
2007-05-27 23:18                       ` Han-Wen Nienhuys
2007-05-28  0:04                         ` Johannes Schindelin
2007-05-28  0:31                           ` Han-Wen Nienhuys
2007-05-27 10:46               ` Johannes Schindelin
2007-05-27 18:50       ` Han-Wen Nienhuys
2007-05-27 19:52         ` GIT on MinGW, with tcltk for gitk Han-Wen Nienhuys
2007-05-27 20:39           ` Aaron Gray
2007-05-27 21:19             ` Han-Wen Nienhuys
2007-05-27 21:24               ` Aaron Gray
2007-05-27 21:39                 ` Aaron Gray
2007-05-27 21:55                   ` Han-Wen Nienhuys
2007-05-27 22:22                     ` Aaron Gray
2007-05-27 22:28                       ` Han-Wen Nienhuys
2007-05-27 22:56                         ` GIT on MinGW - No symbolic links support Aaron Gray
2007-05-27 23:56                           ` Johannes Schindelin
2007-05-29  7:11                             ` Johannes Sixt
2007-05-27 22:22                   ` GIT on MinGW, with tcltk for gitk Han-Wen Nienhuys
2007-05-29 10:54       ` GIT on MinGW problem Johannes Sixt
2007-05-29 11:45         ` Marius Storm-Olsen
2007-05-29 12:10           ` Johannes Sixt
2007-05-29 14:29             ` Han-Wen Nienhuys
2007-05-29 14:49               ` Johannes Sixt
2007-05-29 12:11           ` Johannes Schindelin
2007-05-29 13:05             ` Marius Storm-Olsen
2007-05-29 13:24               ` Johannes Sixt
2007-05-29 14:36                 ` Marius Storm-Olsen
2007-05-29 13:47               ` Johannes Schindelin
2007-05-29 14:13                 ` Johannes Sixt
2007-05-29 15:28                   ` Nguyen Thai Ngoc Duy
2007-05-29 15:47                     ` Johannes Sixt
2007-05-29 18:45                       ` Nguyen Thai Ngoc Duy
2007-05-30  3:03                         ` [PATCH] Make git-k an alias to gitk Johannes Schindelin
2007-05-30  7:06                           ` Johannes Sixt
2007-05-30  2:16                       ` GIT on MinGW problem Han-Wen Nienhuys
2007-05-30  2:39                         ` Johannes Schindelin
2007-05-30  2:57                           ` Shawn O. Pearce
2007-05-30  3:25                             ` [PATCH] Git wrapper: add --redirect-stderr option Johannes Schindelin
2007-05-30  3:38                               ` Shawn O. Pearce
2007-05-30  3:45                                 ` Johannes Schindelin
2007-05-30  3:53                                   ` Shawn O. Pearce
2007-05-30  4:12                                     ` Johannes Schindelin
  -- strict thread matches above, loose matches on Subject: below --
2007-05-12 14:20 GIT on MinGW problem Aaron Gray
     [not found] ` <033501c79710$a2eb0290$0200a8c0@AMD2500>
2007-05-15 19:51   ` Han-Wen Nienhuys
2007-05-16  8:02     ` Johannes Sixt
2007-05-21 18:22       ` Nguyen Thai Ngoc Duy
2007-05-26 23:08         ` Han-Wen Nienhuys

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=46592CFE.40303@xs4all.nl \
    --to=hanwen@xs4all.nl \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.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 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.