Debian编译BitchX指定--with-ssl时无法找到OpenSSL的问题

I’ve dealt with this exact headache before when compiling older autotools-based projects against modern Debian’s OpenSSL packages—let’s break down the most reliable fixes step by step:

• First, install pkg-config (it’s often missing by default)
  Many legacy configure scripts rely on pkg-config to correctly locate library paths and compiler flags, especially when system libraries live in locations the script doesn’t expect. Run this to install it:

  sudo apt update && sudo apt install pkg-config
  

  Verify it can detect your OpenSSL installation with:

  pkg-config --cflags --libs openssl
  

  You should see output like -I/usr/include/openssl -L/usr/lib/x86_64-linux-gnu -lssl -lcrypto. If that works, re-run your original configure command:

  ./configure --with-ssl
  

• Manually specify OpenSSL paths to configure
  If pkg-config doesn’t resolve the issue, the script might be looking in the wrong directories. Debian installs libssl-dev headers in /usr/include/openssl and libraries in /usr/lib/x86_64-linux-gnu/ (for 64-bit systems). Try explicitly pointing configure to these locations:

  ./configure --with-ssl=/usr --with-ssl-lib=/usr/lib/x86_64-linux-gnu
  

  Alternatively, pass the required flags directly via CFLAGS and LDFLAGS:

  CFLAGS="-I/usr/include/openssl" LDFLAGS="-L/usr/lib/x86_64-linux-gnu -lssl -lcrypto" ./configure --with-ssl
  

• Check for OpenSSL version compatibility
  BitchX’s configure script is quite old, and it’s likely checking for deprecated OpenSSL functions like SSLeay—which were removed or renamed in OpenSSL 1.1.0+ (the version you have installed). If the above steps fail, you have two options:

  1. Install the legacy OpenSSL 1.0 dev package (if available on your Debian version):

     sudo apt install libssl1.0-dev
     

     Then run configure with the legacy library path:

     ./configure --with-ssl=/usr/lib/x86_64-linux-gnu/openssl-1.0.0/
     

  2. Patch the configure script to use modern OpenSSL checks. Open the configure file and look for lines that check for SSLeay (e.g., AC_CHECK_LIB(crypto, SSLeay, ...)). Replace that line with a check for a modern function like OPENSSL_version:

     # Original line (or similar):
     AC_CHECK_LIB(crypto, SSLeay, [SSL_LIBS="-lcrypto"], [AC_MSG_ERROR(--with-ssl given, but could not find OpenSSL)])
     # Replace with:
     AC_CHECK_LIB(crypto, OPENSSL_version, [SSL_LIBS="-lcrypto"], [AC_MSG_ERROR(--with-ssl given, but could not find OpenSSL)])
     

     Then install autoconf (if you don’t have it) and regenerate the configure script:

     sudo apt install autoconf && autoconf
     

     Try running ./configure --with-ssl again after this.

• Verify library permissions
  Rarely, permission issues can block configure from accessing the libraries. Run these commands to ensure the files are readable:

  ls -l /usr/lib/x86_64-linux-gnu/libcrypto.so
  ls -l /usr/include/openssl/ssl.h
  

  If they’re owned by root (which is standard), just confirm other users have read access (they should by default).

内容的提问来源于stack exchange，提问作者Jeffrey L. Roberts