From: Junio C Hamano <gitster@pobox.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: <git@vger.kernel.org>
Subject: Re: [BUG] git-2.30.0-rc1 - Transitive OpenLDAP requirement in libcurl
Date: Mon, 21 Dec 2020 10:37:07 -0800 [thread overview]
Message-ID: <xmqqeejjm2ek.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <002001d6d7bd$d03d7e10$70b87a30$@nexbridge.com> (Randall S. Becker's message of "Mon, 21 Dec 2020 12:22:04 -0500")
"Randall S. Becker" <rsbecker@nexbridge.com> writes:
> The NonStop platform does not have an implementation of OpenLDAP, but git is
> attempting to use it. We are getting unresolved references from libcurl,
> which makes references to openldap regardless of whether it exists. We do
> not expect git to use ldap_setup_connection, for example. We need a way of
> disabling the use of this package. This appears to be is a net new for issue
> for 2.23.0, which we just did not get far enough on rc0 to encounter.
I assume "23" on the last line is typo for "30".
Between v2.29.0..v2.30.0-rc1, there is nothing other than 3b990aa6
(push: parse and set flag for "--force-if-includes", 2020-10-03),
which seem to have nothing to do with auth, that touches http*.c or
remote-curl.c
Is it possible that you updated your build procedure and/or options
for libcurl since last time you built a working Git successfully?
If you build v2.29.0 with the same toolchain and library that failed
with -rc1, does the result work OK?
Does NonStop software collection have programs other than Git that
links with libcurl, and if so do they work (in other words, is the
latest source of Git the only thing that suffers from this issue)?
Sorry, I have *no* further suggestions even if you answered any of
the above questions to me, but I hope others (inclusing you and your
folks) may have better insights after answering the above questions
;-)
> Need assistance to resolve this.
>
> Thanks,
> Randall
>
> Sample (there are more) references:
>
> eld command line:
> /usr/bin/eld -o git-imap-send -set systype oss -set highpin on -set
> highrequestor on -set inspect on /usr/lib/ccplmain.o imap-send.o http.o
> common-main.o -L/usr/local/lib -lcurl -lssl -lcrypto -lssl -lcrypto -lz
> -lssl -lcrypto -lcrypto libgit.a xdiff/lib.a -lz -lintl -liconv
> -L/usr/local/lib -lfloss -lutil -lrld -L /G/system/sys04 -lcre -lcrtl
> -lossk -lossf -lsec -li18n -licnv -losse -linet -lossh -lossc
> -allow_duplicate_procs
>
> **** ERROR **** [1210]:
> /usr/local/lib/libcurl.a(libcurl_la-openldap.o): In function
> `ldap_setup_connection':
> libcurl_la-openldap.o(.text._153926392+0x72): unresolved reference to
> ldap_url_parse.
>
>
> -- Brief whoami:
> NonStop developer since approximately 211288444200000000
> UNIX developer since approximately 421664400
> -- In my real life, I talk too much.
next prev parent reply other threads:[~2020-12-21 18:38 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 [this message]
2020-12-21 19:23 ` Randall S. Becker
2020-12-21 20:41 ` Felipe Contreras
2020-12-21 21:02 ` Randall S. Becker
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=xmqqeejjm2ek.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.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).