info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
XCRYPT_2.0 not found
1,262 views
Skip to first unread message
Michael Uplawski
Feb 9, 2020, 9:52:37 AM2/9/20
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Good afternoon
This is a duplicate of a post, I put on Linuxquestions.org. If you
believe that Usenet is dead and won't talk to a phantom, maybe help the
living, over there:
https://www.linuxquestions.org/questions/\
linux-software-2/%5Bruby%5D-xcrypt_2-0-not-found-4175669253/
TIA
- ----------------- Full-quote -------------------
Probably only Debian based systems are concerned.
Anything “Ruby” fails with the following error:
- -------
/lib64/libcrypt.so.1: version `XCRYPT_2.0' not found (required by \
[something])
- -------
The “something” in the square brackets is mostly libruby,
2.5 or 2.7. But when I try to compile a new Ruby-interpreter, the just
created miniruby fails, too, meaning that Ruby is unavailable on my
system. This creates difficulties, as I cannot run the nokogiri XML
parser, which is part of some of my important shell-scripts. Notably
translations btw. French, English and German are affected...
Curiously, before I compiled a brand new, bleeding edge vim 8.2, also
the editor could not be run, neither from the command-line, nor from the
slrn news-reader, nor mutt. With the new version, the error is no longer
happening. I ignore what vim does with libruby.
My libcrypt is 1:4.4.10-10 (Debian) and as far as I am informed, this
version corresponds to XCRYPT_2.0.
Say something funny.
- ---------------- END Full-quote ----------------
- --
GnuPG rsa3072 2018-09-29 [SC] [expires: 2020-09-28]
C36288CD0571D71B0D7642A1688FE966708A032E
sub rsa3072 2018-09-29 [E] [expires: 2020-09-28]
-----BEGIN PGP SIGNATURE-----
iQGzBAEBCgAdFiEEw2KIzQVx1xsNdkKhaI/pZnCKAy4FAl5AHIoACgkQaI/pZnCK
Ay5G+Av/URaFaikCP4sBoc3aqyGizOPgxneLstaNZJ1Jbuq2GhPtODWdpV5RaENR
bzAZsyHkkE6X2cUgh0Snx9WwILHpDug5TGjfUWm8tpu46Zi9jhucmy7nPbUoGDe3
IXWOMeEdKsqbvuMOZ4yXr6WtdwT8Lf5m6CWUh82YaKRUdZtOq4PvAA8ok9vLvRqx
pQTHmlLf30zlMQkpi/AT16zYdrrVOnxpGRNS7yPdUOR5mXHXk8LHgmLrTxkeg7JO
X5tjhKYx+3fdSogQZriCPeDjrigJ6xIBoGlTNmrQuE9q6xvisJewXQgmYXe4/3Gb
XIJM6mS0fQGSPPubbmtZkG2aRI+zXIKpJdUNERrI5V09sgKjvlhpNkwJ33YSDPJH
uuXFV77VULRmx07zmW95hhktaKyiSQPLGNp/M/+gTjimf/Wa8C8HTB2HGiStEoO/
iGzgJMo45Sh6+Cpall5/3EBz1d230agWYqUz/PvsZTxWyGeOKodZ3pH/rejO7naq
tYIEkxd8
=8ow1
-----END PGP SIGNATURE-----
Hash: SHA512
Good afternoon
This is a duplicate of a post, I put on Linuxquestions.org. If you
believe that Usenet is dead and won't talk to a phantom, maybe help the
living, over there:
https://www.linuxquestions.org/questions/\
linux-software-2/%5Bruby%5D-xcrypt_2-0-not-found-4175669253/
TIA
- ----------------- Full-quote -------------------
Probably only Debian based systems are concerned.
Anything “Ruby” fails with the following error:
- -------
/lib64/libcrypt.so.1: version `XCRYPT_2.0' not found (required by \
[something])
- -------
The “something” in the square brackets is mostly libruby,
2.5 or 2.7. But when I try to compile a new Ruby-interpreter, the just
created miniruby fails, too, meaning that Ruby is unavailable on my
system. This creates difficulties, as I cannot run the nokogiri XML
parser, which is part of some of my important shell-scripts. Notably
translations btw. French, English and German are affected...
Curiously, before I compiled a brand new, bleeding edge vim 8.2, also
the editor could not be run, neither from the command-line, nor from the
slrn news-reader, nor mutt. With the new version, the error is no longer
happening. I ignore what vim does with libruby.
My libcrypt is 1:4.4.10-10 (Debian) and as far as I am informed, this
version corresponds to XCRYPT_2.0.
Say something funny.
- ---------------- END Full-quote ----------------
- --
GnuPG rsa3072 2018-09-29 [SC] [expires: 2020-09-28]
C36288CD0571D71B0D7642A1688FE966708A032E
sub rsa3072 2018-09-29 [E] [expires: 2020-09-28]
-----BEGIN PGP SIGNATURE-----
iQGzBAEBCgAdFiEEw2KIzQVx1xsNdkKhaI/pZnCKAy4FAl5AHIoACgkQaI/pZnCK
Ay5G+Av/URaFaikCP4sBoc3aqyGizOPgxneLstaNZJ1Jbuq2GhPtODWdpV5RaENR
bzAZsyHkkE6X2cUgh0Snx9WwILHpDug5TGjfUWm8tpu46Zi9jhucmy7nPbUoGDe3
IXWOMeEdKsqbvuMOZ4yXr6WtdwT8Lf5m6CWUh82YaKRUdZtOq4PvAA8ok9vLvRqx
pQTHmlLf30zlMQkpi/AT16zYdrrVOnxpGRNS7yPdUOR5mXHXk8LHgmLrTxkeg7JO
X5tjhKYx+3fdSogQZriCPeDjrigJ6xIBoGlTNmrQuE9q6xvisJewXQgmYXe4/3Gb
XIJM6mS0fQGSPPubbmtZkG2aRI+zXIKpJdUNERrI5V09sgKjvlhpNkwJ33YSDPJH
uuXFV77VULRmx07zmW95hhktaKyiSQPLGNp/M/+gTjimf/Wa8C8HTB2HGiStEoO/
iGzgJMo45Sh6+Cpall5/3EBz1d230agWYqUz/PvsZTxWyGeOKodZ3pH/rejO7naq
tYIEkxd8
=8ow1
-----END PGP SIGNATURE-----
Michael Uplawski
Feb 13, 2020, 4:16:36 PM2/13/20
to
SOLVED
I set LD_LIBRARY_PATH, now the right version of libcrypt is found and
used.
I set LD_LIBRARY_PATH, now the right version of libcrypt is found and
used.
0 new messages