git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Ævar Arnfjörð Bjarmason'" <avarab@gmail.com>
Cc: <git@vger.kernel.org>
Subject: RE: [BUG] git-2.36.0-rc0 - t6200 fails due to library/path issues
Date: Wed, 6 Apr 2022 11:38:25 -0400	[thread overview]
Message-ID: <045501d849cc$5e2c30a0$1a8491e0$@nexbridge.com> (raw)
In-Reply-To: <220406.867d82e2sr.gmgdl@evledraar.gmail.com>

On April 6, 2022 9:52 AM, Ævar Arnfjörð Bjarmason wrote:
>On Wed, Apr 06 2022, rsbecker@nexbridge.com wrote:
>
>> t6200 makes assumptions that ssh-keygen to be used is located in
>> /usr/local/bin. This causes problems when we have multiple OpenSSL
>> installations - which we do - 3 of them. Our environment supplies
>> OpenSSL
>> 1.1 in /usr/local-ssl1.1, with a corresponding version of ssh-agent in
>> a different directory. There needs to be a mechanism to override the
>> ssh-keygen so that tests will work in this situation.
>>
>> *** RLD ERROR ***: Unresolved Text Symbol
>> OPENSSL_add_all_algorithms_noconf in file /usr/local/bin/ssh-keygen.
>>
>> *** RLD ERROR ***: Unresolved Text Symbol EVP_MD_CTX_cleanup in file
>> /usr/local/bin/ssh-keygen.
>>
>> *** RLD ERROR ***: Unresolved Text Symbol SSLeay in file
>> /usr/local/bin/ssh-keygen.
>>
>> *** RLD ERROR ***: Unresolved Text Symbol EVP_MD_block_size in file
>> /usr/local/bin/ssh-keygen.
>>
>> *** RLD ERROR ***: Unresolved Text Symbol EVP_MD_CTX_init in file
>> /usr/local/bin/ssh-keygen.
>>
>> I do not know why the test is forcing SSH in /usr/local/bin - it is
>> not something coming from our environment, which has PATH set correctly.
>
>Is it:
>
>	SANE_TOOL_PATH = /usr/coreutils/bin:/usr/local/bin
>
>In the nonstop section in config.mak.uname along with:
>
>	Makefile:ifdef SANE_TOOL_PATH
>	Makefile:SANE_TOOL_PATH_SQ = $(subst ','\'',$(SANE_TOOL_PATH))
>	Makefile:BROKEN_PATH_FIX = 's|^\#
>@@BROKEN_PATH_FIX@@$$|git_broken_path_fix "$(SANE_TOOL_PATH_SQ)"|'
>	Makefile:PATH := $(SANE_TOOL_PATH):${PATH}
>	Makefile-else
>	Makefile-BROKEN_PATH_FIX = '/^\# @@BROKEN_PATH_FIX@@$$/d'
>	Makefile-endif
>
>?

I should also point out that we have not previously had path problems like this (2.35.1 and before going back years).


  parent reply	other threads:[~2022-04-06 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 11:18 [BUG] git-2.36.0-rc0 - t6200 fails due to library/path issues rsbecker
2022-04-06 13:51 ` Ævar Arnfjörð Bjarmason
2022-04-06 15:32   ` rsbecker
2022-04-06 15:38   ` rsbecker [this message]
2022-04-06 17:39 ` Junio C Hamano
2022-04-06 18:12   ` rsbecker

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='045501d849cc$5e2c30a0$1a8491e0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    /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).