unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: John Soo <jsoo1@asu.edu>
To: Hamzeh Nasajpour <h.nasajpour@pantherx.org>
Cc: SuarezMiguelC via <help-guix@gnu.org>
Subject: Re: Error in package building : error[E0463]: can't find crate for `openssl_src`
Date: Wed, 21 Oct 2020 05:46:59 -0700	[thread overview]
Message-ID: <c05cda7b-1b56-4c93-98f7-3604323ea8f1@Johns-iPhone> (raw)
In-Reply-To: <12ed5d97-1a39-462b-ab69-71a54d94881e@www.fastmail.com>

     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	other threads:[~2020-10-21 12:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 11:16 Error in package building : error[E0463]: can't find crate for `openssl_src` Hamzeh Nasajpour
2020-10-21 12:46 ` John Soo [this message]
2020-10-21 13:37   ` Hamzeh Nasajpour
2020-10-21 13:40     ` John Soo
2020-10-21 13:46       ` Hamzeh Nasajpour
2020-10-21 13:57         ` Hamzeh Nasajpour
2020-10-21 14:37           ` John Soo
2020-10-22  8:36             ` Hamzeh Nasajpour
2020-10-24 19:47           ` Efraim Flashner
2020-10-25 10:02             ` Hamzeh Nasajpour
2020-11-08 19:32               ` Hamzeh Nasajpour

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c05cda7b-1b56-4c93-98f7-3604323ea8f1@Johns-iPhone \
    --to=jsoo1@asu.edu \
    --cc=h.nasajpour@pantherx.org \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).