From: "Hamzeh Nasajpour" <h.nasajpour@pantherx.org>
To: "John Soo" <jsoo1@asu.edu>
Cc: SuarezMiguelC via <help-guix@gnu.org>
Subject: Re: Error in package building : error[E0463]: can't find crate for `openssl_src`
Date: Thu, 22 Oct 2020 12:06:59 +0330 [thread overview]
Message-ID: <b1564855-f883-4e47-b592-2dbb1378dd49@www.fastmail.com> (raw)
In-Reply-To: <f8cb3fcb-2165-4fc7-968b-1fbd8879731c@Johns-iPhone>
Hello John,
Thanks for your following up.
I put the `openssl` in `inputs` too and the problem wasn't resolved. I also I packaged the `openssl-src` and repackage the `openssl-sys` and this is didn't resolved the problem too.
The point is with the following package definitions the `rust-openssl-sys` will be build/installed without any error, but in the `etebase-py` building/installation I get the previous error.
```
(define-public rust-openssl-src-111.0.1
(package
(name "rust-openssl-src")
(version "111.0.1+1.1.1")
(source
(origin
(method url-fetch)
(uri (crate-uri "openssl-src" version))
(file-name
(string-append name "-" version ".tar.gz"))
(sha256
(base32
"1gpw4zdsi27hg7y4i9xilgfyzp9i56ch5gs64r5ab1gxi3caxvfi"))))
(build-system cargo-build-system)
(arguments
`(#:skip-build? #t
#:cargo-inputs
(("rust-gcc" ,rust-gcc-0.3))))
(home-page "https://github.com/sfackler/rust-openssl")
(synopsis "OpenSSL bindings")
(description "OpenSSL bindings.")
(license license:asl2.0)))
(define-public rust-openssl-sys-0.9
(package
(name "rust-openssl-sys")
(version "0.9.58")
(source
(origin
(method url-fetch)
(uri (crate-uri "openssl-sys" version))
(file-name (string-append name "-" version ".tar.gz"))
(sha256
(base32 "1pkq3x8w16kqvkg75g4w7nny56w9clssww0ibpzg015n153xnhm8"))))
(build-system cargo-build-system)
(arguments
`(#:cargo-inputs
(("rust-libc" ,rust-libc-0.2)
;; Build dependencies:
("rust-autocfg" ,rust-autocfg-1.0)
("rust-cc" ,rust-cc-1)
("rust-pkg-config" ,rust-pkg-config-0.3)
("rust-openssl-src" ,rust-openssl-src-111.0.1)
("rust-vcpkg" ,rust-vcpkg-0.2))))
(native-inputs
`(("openssl" ,openssl)
("pkg-config" ,pkg-config)))
(home-page "https://github.com/sfackler/rust-openssl")
(synopsis "FFI bindings to OpenSSL")
(description
"This package provides FFI bindings to OpenSSL for use in rust crates.")
(license license:expat)))
```
```
phase `patch-cargo-checksums' succeeded after 69.7 seconds
starting phase `build'
Compiling autocfg v1.0.1
Compiling memchr v2.3.3
Compiling lazy_static v1.4.0
Compiling regex-syntax v0.6.18
Compiling libc v0.2.71
Compiling pkg-config v0.3.17
Compiling cc v1.0.58
Compiling bitflags v1.2.1
Compiling foreign-types-shared v0.1.1
Compiling openssl v0.10.30
Compiling cpython v0.3.0
Compiling cfg-if v0.1.10
Compiling thread_local v1.0.1
Compiling foreign-types v0.3.2
Compiling aho-corasick v0.7.13
Compiling num-traits v0.2.12
Compiling regex v1.3.9
Compiling openssl-sys v0.9.58
error[E0463]: can't find crate for `openssl_src`
--> /tmp/guix-build-python-etebase-py-0.30.0.drv-0/etebase-0.30.0/guix-vendor/rust-openssl-sys-0.9.58.tar.xz/build/main.rs:6:1
|
6 | extern crate openssl_src;
| ^^^^^^^^^^^^^^^^^^^^^^^^^ can't find crate
error: aborting due to previous error
For more information about this error, try `rustc --explain E0463`.
error: could not compile `openssl-sys`.
warning: build failed, waiting for other jobs to finish...
error: build failed
command "cargo" "build" "--features" "" "--release" failed with status 101
```
next prev parent reply other threads:[~2020-10-22 8:38 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
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 [this message]
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=b1564855-f883-4e47-b592-2dbb1378dd49@www.fastmail.com \
--to=h.nasajpour@pantherx.org \
--cc=help-guix@gnu.org \
--cc=jsoo1@asu.edu \
/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).