From: aderumier@odiso.com
To: Dietmar Maurer <dietmar@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
pve-devel <pve-devel@pve.proxmox.com>
Subject: Re: [pve-devel] rust build questions
Date: Wed, 05 May 2021 09:18:42 +0200 [thread overview]
Message-ID: <ccfc1be23f9606ed6fc686c4db0b2cacab58c18d.camel@odiso.com> (raw)
In-Reply-To: <1318612504.327.1620196997740@webmail.proxmox.com>
Thanks Dietmar, it's building fine now !
Le mercredi 05 mai 2021 à 08:43 +0200, Dietmar Maurer a écrit :
> > currently, I have tried to build "proxmox" rust
> >
> > https://git.proxmox.com/?p=proxmox.git;a=shortlog
> > with a simple
> > "make deb" + installed needed build depend.
> >
> > but I have this error
> >
> >
> > "
> > test src/tools/websocket.rs - tools::websocket::create_frame (line
> > 161)
> > ... ok
> > test src/tools/websocket.rs - tools::websocket::create_frame (line
> > 148)
> > ... ok
> >
> > failures:
> >
> > ---- src/api/api_type_macros.rs - api_string_type (line 5) stdout -
> > ---
> > error[E0432]: unresolved import `proxmox::api::api`
> > --> src/api/api_type_macros.rs:6:5
> > |
> > 4 | use proxmox::api::api;
> > | ^^^^^^^^^^^^^^^^^ no `api` in `api`
>
> Sorry, this was a bug in the proxmox crate. Please update an test
> again:
>
> commit fa3b5374ed61da3c40a1fc58070d6a16c877c3af (HEAD -> master,
> origin/master, origin/HEAD)
> Author: Dietmar Maurer <dietmar@proxmox.com>
> Date: Wed May 5 08:03:35 2021 +0200
>
> api_type_macros.rs: disable failing doctest (set it to ignore
> instead of no_run)
>
next prev parent reply other threads:[~2021-05-05 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 6:43 Dietmar Maurer
2021-05-05 7:18 ` aderumier [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-05 6:36 aderumier
2021-05-05 6:59 ` Thomas Lamprecht
2021-05-05 7:00 ` Thomas Lamprecht
2021-05-05 7:19 ` aderumier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ccfc1be23f9606ed6fc686c4db0b2cacab58c18d.camel@odiso.com \
--to=aderumier@odiso.com \
--cc=dietmar@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=pve-devel@pve.proxmox.com \
/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