-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solaris platform no longer compiles pppd #458
Comments
Not sure if this is the CI/CD pipeline job on SunOS that itself got an update to OpenSSL that causes it not to load, or the build somehow got changed to omit proper linker statements.. |
@carlsonj any insight? |
@RICCIARDI-Adrien: @enaess has done a ticket here about Solaris... |
I made several tests to try to find a previous version of the Solaris CI that works, but with no success. I suggest to disable the Solaris CI until its action is working again. |
The Solaris Action fix is still in progress, I keep you posted as soon as the maintainer releases a working version. |
With the latest Solaris CI PR (#464) I get the same link error than told in the first comment of this issue : https://github.com/ppp-project/ppp/actions/runs/7085423446/job/19281618388#step:3:2274. |
@paulusmack, @carlsonj, @enaess: Can you look the error? Paul, please merge the @RICCIARDI-Adrien PR to fix Solaris CI: |
Below is the full log of the failing build :
|
@paulusmack, @enaess, @carlsonj, @jkroonza: Can you look for Solaris problem? @RICCIARDI-Adrien has added the log... |
I don't have Solaris, nor a way to reproduce, but looking at the above it looks like the linker is for some reason not pulling in the openssl libraries. We should probably log a separate issue to deal with the warning around volatile, which likely applies to Linux too and should be addressed (probably dropping the volatile keyword should be enough - https://www.kernel.org/doc/html/next/process/volatile-considered-harmful.html - I'm not 100% confident stating that it applies but the logic certainly makes sense, however https://www.embedded.com/introduction-to-the-volatile-keyword/ does give the cases where we want to use volatile, if we do actually need volatile we can likely just cast it away here). |
Right, the failing link command doesn't include any mention of any SSL library. I see the following in the log during the configure phase:
(the first line there looks suspicious to me) and later, in the configuration summary:
@enaess why is there no SSL library on the link command line? Why does configure think we are using OpenSSL when apparently compiling and linking against OpenSSL doesn't work? |
@paulusmack Looks like there was a bug in the ax_check_openssl.m4 where the if condition failed to trigger and search for the right include path. Solaris-11.4 has two versions of openssl (default is 1.0.0 and is compiled with FIPS module support), then openssl-11 is 1.0.2l. They are installed in /usr/openssl/default or /usr/openssl/1.1 respectively. Send you a new PR where configure should be able to pick up the default version by testing the presence of /usr/include/openssl/ssl.h |
@enaess: @paulusmack has been merged your PR: @ all : Now it is good for Solaris? |
@Neustradamus Looks like the latest merge/ci-build as of 2 hours ago completed with the Solaris checks succeeding. |
@enaess: Good job with @RICCIARDI-Adrien! |
Something happened to linking with openssl on SunOS. Multiple unresolved symbols
The text was updated successfully, but these errors were encountered: