-
Notifications
You must be signed in to change notification settings - Fork 38
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
Improve PoCL portability #259
Comments
The gcc ones are in compilersupportlibraries, but we don't have the libc ones anywhere (well, in the compiler shards used by BinaryBuilder, but not easily accessible by anywhere else). |
Maybe I ought to copy stuff over from the sysroot when creating pocl_jll then? |
Uhm, that could work, as long as you don't add them as library products which are automatically dlopened (file products are fine, if you do want to add them, but not necessary) |
Note to self: PoCL is broken on macOS right now because of the switch to
|
PoCL compiles using Clang, which assumes that the host OS provides certain libraries. For example, on Linux:
... or, on macOS:
This is obviously not something we can work with, as we want our artifacts to be stand-alone.
@giordano Do you know where I could get these from, or what is the approach taken on Yggdrasil? CSL_jll seems to only provide
libgcc_s
.The text was updated successfully, but these errors were encountered: