On Fri, 30 Aug 2024 at 09:58, radiatejava <radiatejava@xxxxxxxxx> wrote:
> I am trying to build OpenSSH 9.8p1 with my SSL installed at
> /opt/customssl, but it fails. It fails at the configure cmd itself. It
> does not seem to be honor --with-ssl-dir=/opt/customssl option. What
> could be the issue here?
Assuming your custom thing is API compatible, the usual reason for
this is that it's compiled as a shared library, but is not in the
linker's runtime library path. This will be visible in config.log
(you will need to scroll back past all the defines to find the error).
Depending on your system there's usually a few potential ways to fix it:
1) add the directory path to the system's runtime library search path
2) tell your linker to add the directory to the runtime library search
path (-R/-rpath).
3) link in your thing as a static library.
We use #2 in the regression tests on Linux, which is something like:
$ ./configure --with-ssl-dir=/opt/customssl --with-rpath=-Wl,-rpath,
(note trailing comma is significant) but this may be different on
other platforms or configurations.
--
Darren Tucker (dtucker at dtucker.net)
GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@xxxxxxxxxxx
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
