All of lore.kernel.org
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: [BUG] git-2.36.0-rc0 - t6200 fails due to library/path issues
Date: Wed, 6 Apr 2022 07:18:39 -0400	[thread overview]
Message-ID: <041601d849a8$1441ce60$3cc56b20$@nexbridge.com> (raw)

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.

Thanks,
Randall


             reply	other threads:[~2022-04-06 13:48 UTC|newest]

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

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

  git send-email \
    --in-reply-to='041601d849a8$1441ce60$3cc56b20$@nexbridge.com' \
    --to=rsbecker@nexbridge.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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.