Skip to content

Only define libssp if our CSL intsall actually has it #58175

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

Merged
merged 1 commit into from
Apr 23, 2025

Conversation

staticfloat
Copy link
Member

Some CSL installs (such as those from USE_BINARYBUILDER=0 builds) do not have a libssp, because their GCC was built without stack smash protection, or it was statically linked. This allows our CSL_jll to adapt to that, avoiding issues like those reported in 0.

This should fix #58173

Some CSL installs (such as those from `USE_BINARYBUILDER=0` builds) do
not have a `libssp`, because their GCC was built without stack smash
protection, or it was statically linked.  This allows our CSL_jll to
adapt to that, avoiding issues like those reported in [0].

[0]: #58173
staticfloat added a commit to JuliaCI/julia-buildkite that referenced this pull request Apr 22, 2025
Testing from-source build for
JuliaLang/julia#58175
@staticfloat
Copy link
Member Author

Under test here: JuliaCI/julia-buildkite#443

@staticfloat staticfloat merged commit 947221c into master Apr 23, 2025
4 of 7 checks passed
@staticfloat staticfloat deleted the sf/libssp_dynamism branch April 23, 2025 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

libssp.0 missing error in scheduled from source build
1 participant