All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Igor Korot <ikorot01@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Is support for 10.8 dropped?
Date: Wed, 11 Apr 2018 05:44:05 -0400	[thread overview]
Message-ID: <CAPig+cTw5GjB4VgFD2teDvMuyGPFFoNSCqbXbarEXCe3fVdLjQ@mail.gmail.com> (raw)
In-Reply-To: <CA+FnnTzFomd91d1F6O-a28hXQ6PxOiBd44da4nSVW0MuDKgkmw@mail.gmail.com>

On Wed, Apr 11, 2018 at 12:28 AM, Igor Korot <ikorot01@gmail.com> wrote:
>>> Is there a way to check for OpenSSL presence?
>>
>> Not sure what you're asking. Are you asking how to determine if you
>> already have OpenSSL built on your machine?
>
> Yes, that's what I was asking...

Easiest way to determine it is to try to compile Git without setting NO_OPENSSL.

> This is what I got trying to do just "make":
>
> MyMac:git-2.17.0 igorkorot$ make
>     * new build flags
>     CC credential-store.o
> In file included from credential-store.c:1:
> In file included from ./cache.h:9:
> ./gettext.h:17:11: fatal error: 'libintl.h' file not found
> #       include <libintl.h>
>                 ^
> 1 error generated.

This is because you don't have gettext installed. You should be able
to set NO_GETTEXT to work around this.

> And I am also confused. Which file am I suppose to modify here?
>
> MyMac:git-2.17.0 igorkorot$ ls -la conf*
> -rwxr-xr-x@ 1 igorkorot  staff  74461 Apr  2 10:13 config.c
> -rwxr-xr-x@ 1 igorkorot  staff   9888 Apr  2 10:13 config.h
> -rwxr-xr-x@ 1 igorkorot  staff    540 Apr  2 10:13 config.mak.in
> -rwxr-xr-x@ 1 igorkorot  staff  16940 Apr  2 10:13 config.mak.uname
> -rwxr-xr-x@ 1 igorkorot  staff  37509 Apr  2 10:13 configure.ac
> -rw-r--r--  1 igorkorot  staff  37500 Apr  8 18:52 configure.ac+

You should create a new file named "config.mak". For instance, the
content of your config.mak file might be:

    NO_GETTEXT=Yes

  reply	other threads:[~2018-04-11  9:44 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=CAPig+cTw5GjB4VgFD2teDvMuyGPFFoNSCqbXbarEXCe3fVdLjQ@mail.gmail.com \
    --to=sunshine@sunshineco.com \
    --cc=git@vger.kernel.org \
    --cc=ikorot01@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.