On Aug 15, 2014, at 11:04, Junio C Hamano wrote:
The 10.1.0 anomaly actually was bothering me, too. How
about doing it this way?
-- >8 --
Subject: [PATCH v2] config.mak.uname: add hint on uname_R for MacOS X
I always have to scratch my head every time I see this cryptic
pattern "[15678]\."; l
"Kyle J. McKay" writes:
>> +# i.e. "begins with [15678] and the a dot" means "10.4.* or older".
>
> s/the a dot/a dot/
>
>> ifeq ($(shell expr "$(uname_R)" : '[15678]\.'),2)
>> OLD_ICONV = UnfortunatelyYes
>> NO_APPLE_COMMON_CRYPTO = YesPlease
>
> Otherwise look
On Aug 15, 2014, at 10:02, Junio C Hamano wrote:
By the way, can we document this "uname_R on MacOS X" business
nearby, perhaps like this?
-- >8 --
Subject: config.mak.uname: add hint on uname_R for MacOS X
I always have to scratch my head every time I see this cryptic
pattern "[15678]\."; lea
"Kyle J. McKay" writes:
> The below patch does the right thing. Conveniently there's already
> a test for 10.4 and earlier so only a single line need be added.
>
> --Kyle
>
> 8<
> Subject: [PATCH] config.mak.uname: set NO_APPLE_COMMON_CRYPTO on older systems
>
> Older MacOS systems pri
"Kyle J. McKay" writes:
> On Aug 14, 2014, at 16:18, Junio C Hamano wrote:
>
>> Markus Hitter writes:
>>
The is in Mac OS X 10.6 .. 10.9,
but not in 10.4 (I don't know about 10.5).
>
> That header is new with 10.5
>
>> Is this about platform dependency, or what the end user happens t
Am 15.08.2014 um 00:29 schrieb Jonathan Nieder:
> Orthogonal to that: a patch to the Darwin section of config.mak.uname
> so you can build without the 'make configure' would be even more
> welcome. :)
On this one. You need at least NO_GETTEXT and NO_EXPAT. I've attached a
config.mak.autogen to sh
Am 15.08.2014 um 09:46 schrieb Kyle J. McKay:
> The below patch does the right thing. Conveniently there's already
> a test for 10.4 and earlier so only a single line need be added.
I can confirm this patch works. Thank you very much.
> 8<
> Subject: [PATCH] config.mak.uname: set NO_A
On Fri, Aug 15, 2014 at 3:46 AM, Kyle J. McKay wrote:
> On Aug 14, 2014, at 16:18, Junio C Hamano wrote:
>
>> Markus Hitter writes:
>>
The is in Mac OS X 10.6 .. 10.9,
but not in 10.4 (I don't know about 10.5).
>
> That header is new with 10.5
>
>> Is this about platform dependency, o
On Aug 14, 2014, at 16:18, Junio C Hamano wrote:
> Markus Hitter writes:
>
>>> The is in Mac OS X 10.6 .. 10.9,
>>> but not in 10.4 (I don't know about 10.5).
That header is new with 10.5
> Is this about platform dependency, or what the end user happens to
> choose to install (in other words,
Markus Hitter writes:
>> The is in Mac OS X 10.6 .. 10.9,
>> but not in 10.4 (I don't know about 10.5).
Is this about platform dependency, or what the end user happens to
choose to install (in other words, is there an add-on users of 10.4
can choose to add, which allows them to use that header
Hi Markus,
> export NO_APPLE_COMMON_CRYPTO=yes
> make configure
> CFLAGS=-O2 ./configure --without-tcltk --prefix=/usr/global
> make all
>
> compiles fine on 10.4.10. Would a configure patch checking for the
> existence of CommonHMAC.h and, if not found, defining this variable, be
> acceptable?
Y
Am 14.08.2014 um 16:39 schrieb Torsten Bögershausen:
> On 08/14/2014 02:13 PM, Markus Hitter wrote:
>> Issue 2: I need this simple patch ...
>>
>> --- compat/apple-common-crypto.h.org2014-07-30 23:19:53.0
>> +0200
>> +++ compat/apple-common-crypto.h2014-08-14 12:57:37.0 +020
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
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
14 matches
Mail list logo
