From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Compiling PBS on arm64
Date: Mon, 07 Dec 2020 08:53:31 +0100 [thread overview]
Message-ID: <1607327433.kteohg3dea.astroid@nora.none> (raw)
In-Reply-To: <CAJ-Uffk_gWE9yqFQBn8WzRKf93hu_GtHoraoBj_gLDQNLKTqSw@mail.gmail.com>
On December 6, 2020 8:41 pm, Kamil Trzciński wrote:
> I'm slightly progressing, but I stumbled across some `debcargo` problem. It
> appears that
> Proxmox uses their own fork of `debcargo`, which is needed in order to
> build crates
> without the usage of crates.io. Is this patch published somewhere?
>
> rust-debcargo (2.4.2-pve1) proxmox-rust; urgency=medium
>
> * allow overriding maintainer via debcargo.toml
> * implement local crate support.patch
>
> -- Proxmox Support Team <support@proxmox.com> Tue, 14 Jan 2020 16:13:48
> +0100
https://git.proxmox.com/?p=debcargo-conf.git;a=tree;f=src/debcargo/debian/patches;h=7345cadea4cbffc3174c04e34960e91767892100;hb=refs/heads/proxmox/buster
all of the toolchain backports are published as well on
git.proxmox.com.. if you want to re-compile all of our devel repo for
arm64, I suggest familiarizing yourself with debcargo and the
debcargo-conf repo (especially the upstream and Proxmox readmes) ;)
> On Fri, Dec 4, 2020 at 4:21 PM Kamil Trzciński <ayufan@ayufan.eu> wrote:
>
>> ARM64 is becoming increasingly popular, especially that PBS seems at least
>> for my usage-pattern to be ideal to run on my arm64 NAS. In the end
>> I want to try to be able to recompile everything for arm64 and see how
>> nicely
>> it works there.
>>
>> But first I decided to try to compile all packages for `amd64`. And I'm
>> scratching my head
>> to try to do that. This proves to be super hard due to multitude of
>> dependencies that are backported,
>> unordered, and require a very special set of commands to be executed
>> depending on a git repo
>> since PBS is rust-based.
>>
>> Do you maybe happen to have a comprehensive guide that allows you to
>> compile everything
>> from the scratch without the use of `/devel` repo, ideally with some kind
>> of CI scripts that would do this heavy lifting?
>>
>> Kamil Trzciński
>>
>>
>>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
next prev parent reply other threads:[~2020-12-07 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 15:21 Kamil Trzciński
2020-12-04 15:48 ` Kamil Trzciński
2020-12-06 19:41 ` Kamil Trzciński
2020-12-07 5:32 ` Dietmar Maurer
2020-12-07 7:53 ` Fabian Grünbichler [this message]
2020-12-07 12:42 ` Kamil Trzciński
2020-12-08 10:19 ` Kamil Trzciński
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=1607327433.kteohg3dea.astroid@nora.none \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal