All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: "Lars Schneider" <larsxschneider@gmail.com>,
	"GIT Mailing-list" <git@vger.kernel.org>,
	"Torsten Bögershausen" <tboegi@web.de>
Subject: Re: [RFC] OS X El Capitan + Xcode ships without SSL header?!
Date: Sun, 29 Nov 2015 18:04:54 +0100	[thread overview]
Message-ID: <565B3036.8000604@web.de> (raw)
In-Reply-To: <BBD3F9B1-9FCA-4207-B374-3ADCF19F1431@gmail.com>

On 21/11/15 19:58, Lars Schneider wrote:
> Hi,
> 
> I cannot build Git on a clean machine with OS X El Capitan 10.11, Xcode 7.1.1 and Xcode command line tools because of missing OpenSSL headers.
> 
> It looks like as there are no OpenSSL headers at all. I only found this weird non working version:
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift-migrator/sdk/MacOSX.sdk/usr/include/openssl/ssl.h
> 
> I installed OpenSSL with brew, added the include path and it works.
> 
> Can anyone confirm?
> 
> Thanks,
> Lars
> 
(Does it make sense that you send a patch which auto-detects brew similar to fink or mac ports?)

After some proper updating of one test machine I ran into the same problem.
A possible patch may look like this:


commit 5e7c16f3350e8e62bfdb181b0b5da7352945d046
Author: Torsten Bögershausen <tboegi@web.de>
Date:   Sun Nov 29 17:29:22 2015 +0100

    Mac OS X 10.11: set NO_OPENSSL
    
    There is no openssl/ directory any more in Mac OS X 10.11,
    openssl is depracated since Mac OS X 10.7
    
    Set NO_OPENSSL to YesPlease as default under Mac OS X, and make it
    possible to override this and use openssl by defining DARWIN_OPENSSL

diff --git a/config.mak.uname b/config.mak.uname
index f34dcaa..a8a8b07 100644
--- a/config.mak.uname
+++ b/config.mak.uname
@@ -105,6 +105,12 @@ ifeq ($(uname_S),Darwin)
        ifeq ($(shell test "`expr "$(uname_R)" : '\([0-9][0-9]*\)\.'`" -ge 11 && echo 1),1)
                HAVE_GETDELIM = YesPlease
        endif
+       # MacOS 10.11  and higher
+       ifeq ($(shell test "`expr "$(uname_R)" : '\([0-9][0-9]*\)\.'`" -ge 15 && echo 1),1)
+               ifndef DARWIN_OPENSSL
+                       NO_OPENSSL = YesPlease
+               endif
+       endif
        NO_MEMMEM = YesPlease
        USE_ST_TIMESPEC = YesPlease
        HAVE_DEV_TTY = YesPlease

  parent reply	other threads:[~2015-11-29 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21 18:58 [RFC] OS X El Capitan + Xcode ships without SSL header?! Lars Schneider
2015-11-22 13:12 ` Dair Grant
2015-11-29 17:04 ` Torsten Bögershausen [this message]
2015-12-01  9:04   ` Lars Schneider

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=565B3036.8000604@web.de \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=larsxschneider@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.