From: "Hamzeh Nasajpour" <h.nasajpour@pantherx.org>
To: "Efraim Flashner" <efraim@flashner.co.il>
Cc: SuarezMiguelC via <help-guix@gnu.org>
Subject: Re: Error in package building : error[E0463]: can't find crate for `openssl_src`
Date: Sun, 25 Oct 2020 13:32:50 +0330 [thread overview]
Message-ID: <bbc5ed5c-4e2e-4e9d-bc80-4f7903bbc872@www.fastmail.com> (raw)
In-Reply-To: <20201024194707.GA984@E5400>
Hi Efraim,
> I'd add in a substitution here for openssl like this (untested):
> ;; Don't depend on vendored sources
> (("0.10.30.*") "0.10.30\" }\n")
>
Thanks, I added it and this step passed and now I don't get the previous error in building.
Now I faced with another issue:
```
...
Compiling serde_bytes v0.11.5
Compiling rmp-serde v0.14.3
Compiling sodiumoxide v0.2.6
Compiling reqwest v0.10.4
Compiling etebase v0.1.0
Compiling etebase-python v0.30.0 (/tmp/guix-build-python-etebase-py-0.30.0.drv-0/etebase-0.30.0)
error: unterminated double quote string
--> src/lib.rs:63:44
|
63 | include!(concat!(env!("OUT_DIR"), "/glue.rs"));
| ^^^^^
error: aborting due to previous error
error: could not compile `etebase-python`.
```
This error is related to this line: https://github.com/etesync/etebase-py/blob/64bce73fe2a9a6c82923cd3cedc9210b874f5c01/src/lib.rs#L62
I don't know what's this. And what should I do? Do you have any idea?
Regards,
Hamzeh
next prev parent reply other threads:[~2020-10-25 10:03 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
2020-10-24 19:47 ` Efraim Flashner
2020-10-25 10:02 ` Hamzeh Nasajpour [this message]
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=bbc5ed5c-4e2e-4e9d-bc80-4f7903bbc872@www.fastmail.com \
--to=h.nasajpour@pantherx.org \
--cc=efraim@flashner.co.il \
--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).