From: "Torsten Bögershausen" <tboegi@web.de>
To: Markus Hitter <mah@jump-ing.de>, git@vger.kernel.org
Subject: Re: Git on Mac OS X 10.4.10
Date: Thu, 14 Aug 2014 16:39:16 +0200 [thread overview]
Message-ID: <53ECCA14.40900@web.de> (raw)
In-Reply-To: <53ECA7DB.7060407@jump-ing.de>
On 08/14/2014 02:13 PM, Markus Hitter wrote:
> I'm new to this list, so: Hello everybody!
>
> My backup servers run Mac OS X 10.4.10. Yes, these are old, but very
> reliable and easily up to the task. And Mac OS X 10.4 is the latest OS
> supported there (PowerPC G3).
>
> Recently I tried to upgrade to v2.0.4 (from 1.7.11.4).
>
> Issue 1: I get many of these warnings:
>
> LINK [many cases]
> /usr/bin/ld: warning multiple definitions of symbol _regcomp
> libgit.a(regex.o) definition of _regcomp in section (__TEXT,__text)
> /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/../../../libSystem.dylib(regcomp.So)
> definition of _regcomp
> /usr/bin/ld: warning multiple definitions of symbol _regexec
> libgit.a(regex.o) definition of _regexec in section (__TEXT,__text)
> /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/../../../libSystem.dylib(regexec.So)
> definition of _regexec
> /usr/bin/ld: warning multiple definitions of symbol _regfree
> libgit.a(regex.o) definition of _regfree in section (__TEXT,__text)
> /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/../../../libSystem.dylib(regfree.So)
> definition of _regfree
>
> Is this expected?
No.
Git has its own regcomp() (and the regXXX() ) in ./compat/regex/*, and
for some reasons the linker
picks them both from libgit.a (which is a static library) and the
dynamic library in libSystem.dylib
Either the linker needs to be convinced not to do that (by changing the
command line to the linker,
changing the order of libraries may help, I don't know)
Or each regcomp in the .h and .c files is changed into git_regcomp.
This change shouldn't break anything.
>
>
> Issue 2: I need this simple patch ...
>
> --- compat/apple-common-crypto.h.org 2014-07-30 23:19:53.000000000 +0200
> +++ compat/apple-common-crypto.h 2014-08-14 12:57:37.000000000 +0200
> @@ -2,7 +2,7 @@
> #define OPENSSL_NO_MD5
> #define HEADER_HMAC_H
> #define HEADER_SHA_H
> -#include <CommonCrypto/CommonHMAC.h>
> +//#include <CommonCrypto/CommonHMAC.h>
> #define HMAC_CTX CCHmacContext
> #define HMAC_Init(hmac, key, len, algo) CCHmacInit(hmac, algo, key, len)
> #define HMAC_Update CCHmacUpdate
The <CommonCrypto/CommonHMAC.h> is in Mac OS X 10.6 .. 10.9,
but not in 10.4 (I don't know about 10.5).
You can try to tweak the "makefiles", search for NO_APPLE_COMMON_CRYPTO,
and set NO_APPLE_COMMON_CRYPTO, but only for Darwin 10.3 (or below)
> ... and this command sequence ...
>
> make all
> touch imap-send.o
> touch git-imap-send
> make all
>
> ... to get it compiling. All, except git-imap-send, obviously, which is
> no loss for my purposes.
>
> I tried many releases, the patch requirement started with about v1.9.1,
> the git-imap-send failure somewhere between 1.8.1.6 and 1.8.4.3.
>
> Trying to be a good Open Source citizen, how would I proceed?
If you want to share your changes, please send a patch to this list.
> Thanks,
> Markus
next prev parent reply other threads:[~2014-08-14 14:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 12:13 Git on Mac OS X 10.4.10 Markus Hitter
2014-08-14 14:39 ` Torsten Bögershausen [this message]
2014-08-14 18:39 ` Markus Hitter
2014-08-14 22:29 ` Jonathan Nieder
2014-08-15 12:48 ` Markus Hitter
2014-08-14 23:18 ` Junio C Hamano
2014-08-15 7:46 ` Kyle J. McKay
2014-08-15 9:39 ` Eric Sunshine
2014-08-15 12:34 ` Markus Hitter
2014-08-15 16:29 ` Junio C Hamano
2014-08-15 17:02 ` Junio C Hamano
2014-08-15 17:56 ` Kyle J. McKay
2014-08-15 18:04 ` Junio C Hamano
2014-08-15 18:51 ` Kyle J. McKay
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=53ECCA14.40900@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=mah@jump-ing.de \
/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).