All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Schouten <ed@fxq.nl>
To: git@vger.kernel.org
Subject: Patch for Makefile - LIBMD_SHA1: -lmd on FreeBSD
Date: Tue, 10 Jul 2007 15:19:06 +0200	[thread overview]
Message-ID: <20070710131906.GC55449@hoeg.nl> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 461 bytes --]

Hello,

Once in a while I send in some patches to the FreeBSD folks for the
devel/git port. I just wrote a patch for Git that makes it possible to
link it against the FreeBSD Message Digest library (libmd), removing the
dependency on OpenSSL.

The patch adds the switch LIBMD_SHA1. When set, it just uses sha.h and
-lmd. I've also added proper documentation to the top of the Makefile.

Yours,
-- 
 Ed Schouten <ed@fxq.nl>
 WWW: http://g-rave.nl/

[-- Attachment #1.2: git-libmd.diff --]
[-- Type: text/x-diff, Size: 835 bytes --]

--- Makefile	2007-07-10 15:16:03.000000000 +0200
+++ Makefile	2007-07-10 15:17:31.000000000 +0200
@@ -55,6 +55,9 @@
 # specify your own (or DarwinPort's) include directories and
 # library directories by defining CFLAGS and LDFLAGS appropriately.
 #
+# Define LIBMD_SHA1 environment variable when running make to make use
+# of FreeBSD's libmd SHA1 routines.
+#
 # Define PPC_SHA1 environment variable when running make to make use of
 # a bundled SHA1 routine optimized for PowerPC.
 #
@@ -637,6 +640,10 @@
 	BASIC_CFLAGS += -DOLD_ICONV
 endif
 
+ifdef LIBMD_SHA1
+	SHA1_HEADER = "sha.h"
+	EXTLIBS += -lmd
+else
 ifdef PPC_SHA1
 	SHA1_HEADER = "ppc/sha1.h"
 	LIB_OBJS += ppc/sha1.o ppc/sha1ppc.o
@@ -654,6 +661,7 @@
 endif
 endif
 endif
+endif
 ifdef NO_PERL_MAKEMAKER
 	export NO_PERL_MAKEMAKER
 endif

[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]

                 reply	other threads:[~2007-07-10 13:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070710131906.GC55449@hoeg.nl \
    --to=ed@fxq.nl \
    --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.