From: Lee Lists <lists@jave.fr>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE user list <pve-user@lists.proxmox.com>,
PVE User List <pve-user@pve.proxmox.com>,
pve-devel <pve-devel@pve.proxmox.com>,
pbs-devel <pbs-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PVE-User] Proxmox Backup Server (beta)
Date: Fri, 9 Oct 2020 14:10:30 +0200 (CEST) [thread overview]
Message-ID: <1534342370.13066.1602245430784.JavaMail.zimbra@jave.fr> (raw)
Hi Thomas,
Thank you, it was effectively a missing clang installation.
Finally i managed to compile pbs on armbian / aarch64 (https://kobol.io/).
First tests gives good results on this rk3399 platform.
┌───────────────────────────────────┬───────────────────┐
│ Name │ Value │
╞═══════════════════════════════════╪═══════════════════╡
│ TLS (maximal backup upload speed) │ not tested │
├───────────────────────────────────┼───────────────────┤
│ SHA256 checksum computation speed │ 885.79 MB/s (44%) │
├───────────────────────────────────┼───────────────────┤
│ ZStd level 1 compression speed │ 139.33 MB/s (19%) │
├───────────────────────────────────┼───────────────────┤
│ ZStd level 1 decompression speed │ 326.64 MB/s (27%) │
├───────────────────────────────────┼───────────────────┤
│ Chunk verification speed │ 271.91 MB/s (36%) │
├───────────────────────────────────┼───────────────────┤
│ AES256 GCM encryption speed │ 561.27 MB/s (15%) │
└───────────────────────────────────┴───────────────────┘
Regards,
Lee
----- Mail original -----
De: "Thomas Lamprecht" <t.lamprecht@proxmox.com>
À: "Proxmox VE user list" <pve-user@lists.proxmox.com>, "Lee Lists" <lists@jave.fr>
Cc: "PVE User List" <pve-user@pve.proxmox.com>, "pbs-devel" <pbs-devel@lists.proxmox.com>, "pve-devel" <pve-devel@pve.proxmox.com>
Envoyé: Jeudi 8 Octobre 2020 10:21:47
Objet: Re: [PVE-User] Proxmox Backup Server (beta)
On 06.10.20 15:12, Lee Lists wrote:
> I'm trying to build proxmox backup server from source,
> but the build failed in compiling zstd lib bindings.
>
> Any clues ?
Some more hints about the build environment and the executed steps would
be great.
Are all build dependencies installed, this error comes sometimes up if
clang isn't correctly installed.
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next reply other threads:[~2020-10-09 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 12:10 Lee Lists [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-10 10:56 [pve-devel] " Martin Maurer
2020-10-06 13:12 ` [pve-devel] [PVE-User] " Lee Lists
2020-10-08 8:21 ` Thomas Lamprecht
2020-10-09 9:27 ` Lee Lists
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=1534342370.13066.1602245430784.JavaMail.zimbra@jave.fr \
--to=lists@jave.fr \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-devel@pve.proxmox.com \
--cc=pve-user@lists.proxmox.com \
--cc=pve-user@pve.proxmox.com \
--cc=t.lamprecht@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