diff options
| author | Zack Weinberg <zackw@panix.com> | 2020-12-30 14:24:41 -0500 |
|---|---|---|
| committer | Zack Weinberg <zackw@panix.com> | 2020-12-30 14:24:41 -0500 |
| commit | a5b0a665368cc80931a037eecf1f79ede98f397e (patch) | |
| tree | 6c2c5b069ed60e790d5525fd71c812737cde2b19 /Makefile.am | |
| parent | 0ad75cb4a9b6c26252db9c11155afd1388bf42ae (diff) | |
| download | libxcrypt-a5b0a665368cc80931a037eecf1f79ede98f397e.tar.gz libxcrypt-a5b0a665368cc80931a037eecf1f79ede98f397e.tar.bz2 libxcrypt-a5b0a665368cc80931a037eecf1f79ede98f397e.zip | |
test/symbols-compat.sh: Don’t rely on -lcrypt to find libcrypt.so.1.
Some Linux distributions are now shipping libcrypt.so as a symlink to
libcrypt.so.2, but still providing libcrypt.so.1 as a compatibility
library. The symbols-compat.sh test is still relevant on these
systems, but linking a test program against -lcrypt will not find
libcrypt.so.1. Instead use gcc -print-file-name=libcrypt.so.1, which
will find that library regardless of what other libcrypt* files are
present.
This also has the nice fringe benefit that we don’t have to parse ldd
output anymore.
This does *not* fix the symbols-compat failures in CI, but it should
not make them worse.
Diffstat (limited to 'Makefile.am')
0 files changed, 0 insertions, 0 deletions