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: [NOT BUG] git-2.30.0-rc1 - Transitive OpenLDAP requirement in libcurl
Date: Mon, 21 Dec 2020 17:45:31 -0500 [thread overview]
Message-ID: <004701d6d7ea$ffd61e70$ff825b50$@nexbridge.com> (raw)
On December 21, 2020 4:03 PM, I wrote:
> To: 'Felipe Contreras' <felipe.contreras@gmail.com>; 'Junio C Hamano'
> <gitster@pobox.com>
> Cc: 'git@vger.kernel.org' <git@vger.kernel.org>
> Subject: RE: [BUG] git-2.30.0-rc1 - Transitive OpenLDAP requirement in
> libcurl
>
> 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?
Well, looks like this probably an operator issue. I tried the build in a clean environment (our official Jenkins build environment) and 2.30.0-rc1 builds and is currently in testing on both NonStop platforms. Something is likely messed up in my clone. There's nothing in the environment that is weird. So it's obviously something I did, but I don't really know what (maybe git reset --hard master && git clean -dxf is not a sufficient reset).
Moving forward,
Randall
next reply other threads:[~2020-12-21 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 22:45 Randall S. Becker [this message]
2020-12-22 0:12 ` [NOT BUG] git-2.30.0-rc1 - Transitive OpenLDAP requirement in libcurl Felipe Contreras
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='004701d6d7ea$ffd61e70$ff825b50$@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.
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).