From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Felipe Contreras'" <felipe.contreras@gmail.com>,
"'Junio C Hamano'" <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: RE: [BUG] git-2.30.0-rc1 - Transitive OpenLDAP requirement in libcurl
Date: Mon, 21 Dec 2020 16:02:53 -0500 [thread overview]
Message-ID: <004601d6d7dc$a99af4d0$fcd0de70$@nexbridge.com> (raw)
In-Reply-To: <5fe108752910_f93820887@natae.notmuch>
On December 21, 2020 3:41 PM, Felipe Contreras wrote:
> To: Randall S. Becker <rsbecker@nexbridge.com>; 'Junio C Hamano'
> <gitster@pobox.com>
> Cc: git@vger.kernel.org
> Subject: RE: [BUG] git-2.30.0-rc1 - Transitive OpenLDAP requirement in
> libcurl
>
> Randall S. Becker wrote:
> > git is the only product my group builds that uses libcurl. There is a
> > less functional version of libcurl that comes with the operating
> > system that we ignore. We are not linking with that version. The
> > version of curl we have, we built but not since 2.29.2.
> > So I'm confused.
>
> Could be: b990f02fd8 (config.mak.uname: remove unused
> NEEDS_SSL_WITH_CURL flag, 2020-11-11)
>
> It seems it was attempting to only remove NEEDS_SSL_WITH_CURL, which
> indeed wasn't used anymore, but it also removed:
I wondered about this one. I have rolled this back, with no positive effect. The 2.30.0-rc1 build works fine on the x86 platform (currently under test) but not on the Itanium (older) so I'm not suspecting this issue.
> #NO_CURL = YesPlease
We have been building with Curl for years, so probably not this.
> I've no idea about these systems, but a quick search makes me wonder if
> perhaps this was not intended.
Is there some detection going on about OpenLDAP?
prev parent reply other threads:[~2020-12-21 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 17:22 [BUG] git-2.30.0-rc1 - Transitive OpenLDAP requirement in libcurl Randall S. Becker
2020-12-21 18:37 ` Junio C Hamano
2020-12-21 19:23 ` Randall S. Becker
2020-12-21 20:41 ` Felipe Contreras
2020-12-21 21:02 ` Randall S. Becker [this message]
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='004601d6d7dc$a99af4d0$fcd0de70$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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 NNTP newsgroup(s).