[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Error in package building : error[E0463]: can't find crate for `open

From: Hamzeh Nasajpour
Subject: Re: Error in package building : error[E0463]: can't find crate for `openssl_src`
Date: Wed, 21 Oct 2020 17:07:24 +0330
User-agent: Cyrus-JMAP/3.3.0-502-gfef6c88-fm-20201019.001-gfef6c888

Hello John,

Thanks for your quick reply.

But as you see in `Cargo.toml`, this feature mentioned and I think it's needed. 
In the other side setting the `OPENSSL_DIR` didn't resolve my issue.

Do you have any other suggestion?

Can I repackage `rust-openssl-sys-0.9` and remove this line in the package 
definition? (Sorry I'm not expert in rust and I don't know what's the 
`vendored` feature, but I need this package urgently - `etebasepy` )

      (patches (search-patches "rust-openssl-sys-no-vendor.patch"))


On Wed, Oct 21, 2020, at 4:16 PM, John Soo wrote:
> Hello Hamzeh,
> Take a look at gnu/packages/crates-io.scm for other examples of 
> rust-openssl. We try to avoid vendored sources. Recent versions of 
> rust-openssl-sys also complicate this by requiring particular versions 
> of openssl.  While it’s nice that they are explicit about the 
> dependency, we don’t have them in the package set. 
> Finally and probably most immediately useful to you, check out 
> gnu/packages/rust-apps.scm. You may need to set the OPENSSL_DIR 
> environment variable to the location of the openssl dependency.
> I see the “vendored” feature in the Cargo.toml that makes me think this 
> may not work, but that would be where I start. 
> Good luck,
> John

reply via email to

[Prev in Thread] Current Thread [Next in Thread]