mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Beat Bolli <>
To: Nirmal Khedkar <>
Cc: Johannes Schindelin <>,
Subject: Re: Facing error in git-imap-send while compiling Git
Date: Fri, 31 Jan 2020 00:03:08 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Nirmal!

On 30.01.20 21:26, Nirmal Khedkar wrote:
> Hi All,
> I'll admit I'm quite perplexed with this OpenSSL problem that I'm
> facing. Here's what I've done along with their results:

... snipped ...

> Please let me know where am I going wrong. If there's any other system
> packages that I can download so that I can focus on other Git issues
> and this one simultaneously, please let me know. Here are my system
> specifications (let me know if you need anything more specific):
> ---
> OS: Ubuntu 18.04
> Linux Kernel: 5.3
> OpenSSL Version: 1.1.1d
> ---
> Apologies for the long email,
> Thank You,

No problem!

My system is similar: Debian testing with the OpenSSL 1.1.1d from the
distribution. I have no build problems whatsoever. OpenSSL comes with
backward compatibility macros that most allow code written for 1.0.2 to
be compiled without errors. These macros can be turned off by changing
the API compatibility version using -DOPENSSL_API_COMPAT=<version>.

You can check this with

    make V=1 imap-send.o

This will show the compiler command executed:

    gcc -o imap-send.o -c -MF ./.depend/imap-send.o.d -MQ imap-send.o
-MMD -MP   -g -O2 -I. -DHAVE_SYSINFO -DGIT_HOST_CPU="\"x86_64\""
-DSHA1DC_CUSTOM_INCLUDE_UBC_CHECK_C="\"git-compat-util.h\"" -DSHA256_BLK

Check it for any -D flags mentioning OpenSSL.

You can get even more verbose output from gcc by copying the compiler
command make displays and running it after appending the verbose flag
"-v" at the end.

Check this new output for include directories etc. You need to make sure
that gcc picks up the system OpenSSL include files. They should be found
under /usr/include/openssl.

Hope this helps,

Beat Bolli

  reply	other threads:[~2020-01-30 23:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 19:20 Facing error in git-imap-send while compiling Git Nirmal Khedkar
2020-01-16 22:51 ` Junio C Hamano
2020-01-17 12:42   ` Nirmal Khedkar
2020-01-17 13:35     ` Johannes Schindelin
2020-01-20 19:12       ` Nirmal Khedkar
2020-01-20 21:35         ` Johannes Schindelin
2020-01-21 11:50           ` Nirmal Khedkar
2020-01-21 18:11             ` Junio C Hamano
2020-01-21 21:09             ` Johannes Schindelin
2020-01-22 19:20               ` Junio C Hamano
2020-01-30 20:26                 ` Nirmal Khedkar
2020-01-30 23:03                   ` Beat Bolli [this message]
2020-02-01 21:35                   ` Johannes Schindelin
2020-02-15 14:00                     ` Nirmal Khedkar
  -- strict thread matches above, loose matches on Subject: below --
2020-02-17  9:30 Abhishek Kumar

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:

  List information:

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

  git send-email \ \ \ \ \ \

* 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

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).