Missing constants for x86_64-unknown-linux-gnu about rust-cryptoki HOT 6 OPEN

Ok, sorry for the huge delay.

So, it seems when we branched out cryptoki-0.3.x to release Parsec back in March, we branched from the latest v0.3 of cryptoki. We made some changes to cryptoki-sys and upstreamed that as 0.1.5 - however the problem here is that we had added other stuff to cryptoki-sys since that v0.3 of cryptoki. Which means this newest version of cryptoki-sys is actually missing some stuff that is present in main.

My suggestions here are:

• we bump the main version of cryptoki-sys to 0.1.6 and release that ASAP (see #138 )
• we yank 0.1.5 of cryptoki

Apologies everyone for this mistake, it is yet another lesson in juggling the versions of two interdependent crates in the same repo :[

cc @gowthamsk-arm - I don't think this would affect Parsec in any way.

from rust-cryptoki.

Update: I have released v0.1.6 of cryptoki-sys. I'll be yanking 0.1.5 tomorrow.

from rust-cryptoki.

I can reproduce this problem. Adding generate-bindings feature does not help.

I did succeed when I used crate directly via git: cryptoki = { version = "0.4.1", git = "https://github.com/parallaxsecond/rust-cryptoki" }. Maybe recent changes in #130 helped?

from rust-cryptoki.

I'm having the same problems. These constants disappeared in packaged pkcs11.h of [email protected]:

296d295
< #define CKF_ERROR_STATE		(1UL << 24)
1048,1049d1046
< #define CKF_EC_F_2M		(1UL << 21)
< #define CKF_EC_ECPARAMETERS	(1UL << 22)

from rust-cryptoki.

I'm having the same problem.

It seems as though there may have been error releasing or tagging.

cryptoki-0.4.1 was created on 2022-09-29.
cryptoki-0.4.0 was created on 2022-09-07.
cryptoki-0.3.0 was created on 2022-01-14.

Then, on 2023-03-15, cryptoki-0.3.1 and cryptoki-sys-0.1.5 were created on the cryptoki-0.3.0 branch. Crates.io shows the cryptoki-sys dep for cryptoki as "^0.1.4", so cargo selects 0.1.5.

If I manually say cryptoki-sys = "=0.1.4" in my Cargo.toml, I can build. Of course, this means you're depending on a cryptoki-sys that is 9 months older than cryptoki...

from rust-cryptoki.

cryptoki-sys 0.1.5 doesn't seem to be yanked.

from rust-cryptoki.