-
Notifications
You must be signed in to change notification settings - Fork 53
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
Linker issue with blst-msm #4
Comments
I got a fix via side-channel. You need to include diff --git a/poc/blst-cuda/build.rs b/poc/blst-cuda/build.rs
index a44513b..367552b 100644
--- a/poc/blst-cuda/build.rs
+++ b/poc/blst-cuda/build.rs
@@ -115,7 +115,7 @@ fn main() {
if let Some(include) = env::var_os("DEP_SPPARK_ROOT") {
nvcc.include(include);
}
- nvcc.file("cuda/pippenger_inf.cu").compile("blst_cuda_msm");
+ nvcc.file("cuda/pippenger.cu").compile("blst_cuda_msm");
println!("cargo:rustc-cfg=feature=\"cuda\"");
println!("cargo:rerun-if-changed=cuda"); |
PoCs are not meant to be used as dependency, but as an example of how to use sppark as dependency. |
Agreed. But I'd expect it to to be a working example, so that one can then use it as a template for your own stuff. When it's not a PoC for working |
And it's working. You do Just in case, I do recognize your problem, which is effectively rooted in poor messaging from our side. At this point I reckon that it would be more efficient if we use more interactive means of communications to move forward. More interactive than github issues that is :-) |
The POC isn't meant to be used with blstrs types (although the code is there), hence I'm closing this issue. |
I get an error like
when trying to use
blst-msm
as a dependency. Steps to reproduce (you can copy&paste that into your terminal and execute it directly):I'm on Debian.
The text was updated successfully, but these errors were encountered: