-
Notifications
You must be signed in to change notification settings - Fork 486
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
Build problems in rust-secp256k1 after #780 #852
Comments
Can you provide the |
Sure. So, the repo is here: https://github.com/rust-bitcoin/rust-secp256k1/tree/14e82186d1f9d6a0054d0c8982ce28b30c76b874 -- the The dependency pattern is that Specifically, if you clone that repo, to reproduce:
The relevant Cargo.tomls are: Cargo.toml
secp256k1-sys/Cargo.toml
no_std_test/Cargo.toml
I will try to create a minimum reproducable case in the coming week, though I've got some (happy) family stuff that is likely to distract me for the next little while. |
Thanks, can reproduce on |
It's still unclear to me how #780 causes this problem though, given that it doesn't modify how the command is created and what args/envs are passed https://github.com/rust-lang/cc-rs/pull/780/files#diff-b1a35a68f14e696205874893c07fd24fdb88882b47c23cc0e0c80a30c7d53759R1344 |
P.S. for the AFAIK you would have to do |
That means you need to update your Edition to 2021 (or, if you use a workspace, add |
We could perhaps turn default features off for |
Between
cc
1.0.79 and 1.0.80 the "no-std test with ASAN" CI test in rust-secp256k1 stopped working. There was a six-month gap in this release but nothing major or dramatic happened. Bisection tells me that the problem started occurring after the merge of #780.The error I get is during build, and looks like
where the snipped output is a pile of more "cannot find
memcpy
" type errors from various crates, including libcore. If I compile with 57853c4, the previous commit before this one, and force a linker error by adding an unimplemented function (not sure how else to get the exactcc
command), the outputt looks likeIf you compare these two invocations you will see that the latter has
-lc
-lm
-lrt
-lpthread
while the former does not. I guess that-lc
is what's causing errors related to memcpy being undefined.I've read the code in this PR a few times and can't see any way that it would cause these linker flags to get dropped, but empirically that's what appears to be happening.
Originally posted by @apoelstra in #780 (comment)
The text was updated successfully, but these errors were encountered: