git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: "Totsten Bögershausen" <tboegi@web.de>
Cc: Igor Korot <ikorot01@gmail.com>, git <git@vger.kernel.org>
Subject: Re: Is support for 10.8 dropped?
Date: Mon, 23 Apr 2018 17:04:34 -0400	[thread overview]
Message-ID: <CAPig+cSbAaNby++AvCx4CkJ0KcRkx5Q=xs8VSbNmY=dgi-F9jg@mail.gmail.com> (raw)
In-Reply-To: <05560086-232c-f14c-f82b-e21b7ecce1b3@web.de>

On Mon, Apr 23, 2018 at 3:58 PM, Totsten Bögershausen <tboegi@web.de> wrote:
> On 2018-04-23 18:53, Eric Sunshine wrote:
>> On Mon, Apr 23, 2018 at 12:31 PM, Igor Korot <ikorot01@gmail.com> wrote:
>>> 1. Is the file name "config.mak" or "config.make"?
>>
>> "config.mak"
>
> I am confused, I have these file in my tree:
> config.mak.in  config.mak.uname   Makefile
> Setting options is documentend in Makefile

You can place custom build settings in a file named "config.mak" which
you create; it's not part of the distribution. The other files are not
intended for modification.

> I would actually try to install openssl / openssl-dev (or however it is
> called) via "mac ports" or "home brew".
>
> Both should work (but I don't have a system to test on)

Igor indicated earlier[1] in the thread that he wanted to avoid
Homebrew (and Macports, etc., presumably). If he'd be willing to use
Homebrew, then easiest would be simply to install Git itself via
Homebrew: "brew install git"

[1]: https://public-inbox.org/git/CA+FnnTzfJMBuSMAD7PgUurRu8jOpirEgM6=+=i91zdGLWmfUpg@mail.gmail.com/

  reply	other threads:[~2018-04-23 21:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 19:48 Is support for 10.8 dropped? Igor Korot
2018-04-05 21:46 ` Eric Sunshine
2018-04-07  2:20   ` Igor Korot
2018-04-07  7:32     ` Eric Sunshine
2018-04-08 21:10       ` Igor Korot
2018-04-08 22:37         ` Igor Korot
2018-04-08 23:23           ` Eric Sunshine
     [not found]             ` <CA+FnnTwvnA90nDARKW9r7p5iraoOGTvfDJ26n6Udc68bDSUASw@mail.gmail.com>
2018-04-08 23:59               ` Eric Sunshine
2018-04-11  4:28                 ` Igor Korot
2018-04-11  9:44                   ` Eric Sunshine
2018-04-22  5:15                     ` Igor Korot
2018-04-22  5:37                       ` Eric Sunshine
2018-04-22  7:10                         ` Perry Hutchison
2018-04-22 17:49                           ` brian m. carlson
2018-04-23 16:39                             ` Igor Korot
2018-04-23 16:31                         ` Igor Korot
2018-04-23 16:53                           ` Eric Sunshine
2018-04-23 19:58                             ` Totsten Bögershausen
2018-04-23 21:04                               ` Eric Sunshine [this message]
2018-04-23 21:21                                 ` Igor Korot
2018-04-23 23:16                                   ` Perry Hutchison
2018-05-07 15:20                                     ` Igor Korot

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPig+cSbAaNby++AvCx4CkJ0KcRkx5Q=xs8VSbNmY=dgi-F9jg@mail.gmail.com' \
    --to=sunshine@sunshineco.com \
    --cc=git@vger.kernel.org \
    --cc=ikorot01@gmail.com \
    --cc=tboegi@web.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).