From: Junio C Hamano <junkio@cox.net>
To: "Peter Eriksen" <s022018@student.dtu.dk>
Cc: git@vger.kernel.org, Patrick Mauritz <oxygene@studentenbude.ath.cx>
Subject: Re: /bin/sh portability question
Date: Fri, 23 Sep 2005 02:07:07 -0700 [thread overview]
Message-ID: <7vmzm4duf8.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050923075058.GA25473@bohr.gbar.dtu.dk> (Peter Eriksen's message of "Fri, 23 Sep 2005 09:50:58 +0200")
"Peter Eriksen" <s022018@student.dtu.dk> writes:
> It seems things are progressing nicely with regard to
> Solaris portability.
Good to have a Solaris user. I have one patch that I've been
keeping in the proposed updates branch, waiting for a
comfirmation or 'not-good-enough-for-me' answer from people that
have cURL installed in nonstandard places.
------------
Subject: [PATCH] CURLDIR in Makefile
From: Patrick Mauritz <oxygene@studentenbude.ath.cx>
Date: 1127139079 +0200
Support systems that do not install curl headers and libraries
in /usr/{include,lib}.
Signed-off-by: Patrick Mauritz <oxygene@studentenbude.ath.cx>
Signed-off-by: Junio C Hamano <junkio@cox.net>
---
Makefile | 12 +++++++++++-
1 files changed, 11 insertions(+), 1 deletions(-)
a5ebfc164f8380eb4c1c2ff92082687c3cb0b39d
diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -9,6 +9,9 @@
# Define NO_CURL if you do not have curl installed. git-http-pull is not
# built, and you cannot use http:// and https:// transports.
#
+# Define CURLDIR=/foo/bar if your curl header and library files are in
+# /foo/bar/include and /foo/bar/lib directories.
+#
# Define NO_STRCASESTR if you don't have strcasestr.
#
# Define PPC_SHA1 environment variable when running make to make use of
@@ -131,6 +134,13 @@ ifdef WITH_SEND_EMAIL
endif
ifndef NO_CURL
+ ifdef CURLDIR
+ # This is still problematic -- gcc does not want -R.
+ CFLAGS += -I$(CURLDIR)/include
+ CURL_LIBCURL = -L$(CURLDIR)/lib -R$(CURLDIR)/lib -lcurl
+ else
+ CURL_LIBCURL = -lcurl
+ endif
PROGRAMS += git-http-fetch
endif
@@ -285,7 +295,7 @@ git-ssh-upload: rsh.o
git-ssh-pull: rsh.o fetch.o
git-ssh-push: rsh.o
-git-http-fetch: LIBS += -lcurl
+git-http-fetch: LIBS += $(CURL_LIBCURL)
git-rev-list: LIBS += $(OPENSSL_LIBSSL)
init-db.o: init-db.c
next prev parent reply other threads:[~2005-09-23 9:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 7:50 /bin/sh portability question Peter Eriksen
2005-09-23 8:24 ` Junio C Hamano
[not found] ` <54643.10.10.10.28.1127466177.squirrel@linux1>
2005-09-23 9:02 ` Sean
2005-09-23 9:19 ` Junio C Hamano
[not found] ` <39450.10.10.10.28.1127471685.squirrel@linux1>
2005-09-23 10:34 ` Sean
2005-09-25 19:26 ` Nico -telmich- Schottelius
[not found] ` <33541.10.10.10.28.1127677005.squirrel@linux1>
2005-09-25 19:36 ` Sean
2005-09-23 9:07 ` Junio C Hamano [this message]
2005-09-23 12:17 ` Peter Eriksen
2005-09-24 1:13 ` Junio C Hamano
[not found] ` <20050924195029.GA20514@bohr.gbar.dtu.dk>
2005-09-24 21:31 ` Junio C Hamano
2005-09-24 17:35 ` Patrick Mauritz
2005-09-23 19:48 ` H. Peter Anvin
2005-09-23 19:55 ` Morten Welinder
2005-09-23 19:57 ` Joel Becker
2005-09-23 20:00 ` H. Peter Anvin
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=7vmzm4duf8.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=oxygene@studentenbude.ath.cx \
--cc=s022018@student.dtu.dk \
/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).