about summary refs log tree commit diff
path: root/crypt/Versions
diff options
context:
space:
mode:
authorZack Weinberg <zack@owlfolio.org>2023-09-21 14:58:05 -0400
committerZack Weinberg <zack@owlfolio.org>2023-09-21 16:24:59 -0400
commit46e817c4982dfda6aaf6863c141b2e56cfc75acd (patch)
tree7adb7aafbfc6d34a79cb729babfb4786996f9ce2 /crypt/Versions
parent0a19410103c1c4890753596e294438786fa13a8c (diff)
downloadglibc-zack/remove-libcrypt.tar.gz
glibc-zack/remove-libcrypt.tar.xz
glibc-zack/remove-libcrypt.zip
Remove all of the remaining libcrypt code. zack/remove-libcrypt
Completing the removal of libcrypt, delete all of its actual code.
This patch contains only file removals:

git rm -r crypt
git rm include/crypt.h
git rm $(find sysdeps -name libcrypt.abilist)
git rm $(find sysdeps -name fips-private.h)
git rm $(find sysdeps -name 'md5-*' -o -name 'sha256-*' -o -name 'sha512-*')

For this patch (not the earlier ones, I'd still be waiting) I ran the
complete testsuite and found no *new* failures.  26 tests are failing
on my machine due to probable environment issues, but they were all
failing on trunk before I started making changes, and none of them
appear to have anything to do with this patchset.
Diffstat (limited to 'crypt/Versions')
-rw-r--r--crypt/Versions5
1 files changed, 0 insertions, 5 deletions
diff --git a/crypt/Versions b/crypt/Versions
deleted file mode 100644
index 389e7d544a..0000000000
--- a/crypt/Versions
+++ /dev/null
@@ -1,5 +0,0 @@
-libcrypt {
-  GLIBC_2.0 {
-    crypt; crypt_r; encrypt; encrypt_r; fcrypt; setkey; setkey_r;
-  }
-}