From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Tianyu Chen <billchenchina2001@gmail.com>,
Wolfgang Bumiller <w.bumiller@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Zenithal <i@zenithal.me>
Subject: Re: [pve-devel] Building proxmox on riscv64 Debian Sid
Date: Tue, 21 Feb 2023 15:32:04 +0100 (CET) [thread overview]
Message-ID: <1720488798.1037.1676989924484@webmail.proxmox.com> (raw)
> Tianyu Chen <billchenchina2001@gmail.com> hat am 21.02.2023 13:53 CET geschrieben:
> On Tue, Feb 21, 2023 at 12:14:04PM +0100, Wolfgang Bumiller wrote:
>
> > You can build from that, or, since they're actually source-only
> > packages, you could fixup the architecture on the deb files from our
> > bullseye repo directly (dpkg-deb --extract, sed, dpkg-deb --build) and
> > use it that way ;-)
>
> Haha dpkg-deb --extract is a nice trick! I've done it before for some
> packages. debcargo use `Architecture: any` for librust-*-dev files but I
> believe they could be installed for `all`.
there's actually a reason for that - having librust-*-dev as arch:any is required for cross-compiling/multi-arch support (not something we do (yet) in Proxmox, but relevant for Debian), where arch:all would pull in non-rust transitive build dependencies from the wrong arch.
next reply other threads:[~2023-02-21 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 14:32 Fabian Grünbichler [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-27 7:36 Fabian Grünbichler
2023-02-21 14:37 Fabian Grünbichler
[not found] <mailman.261.1676973980.376.pve-devel@lists.proxmox.com>
2023-02-21 11:14 ` Wolfgang Bumiller
2023-02-21 11:19 ` Fabian Grünbichler
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=1720488798.1037.1676989924484@webmail.proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=billchenchina2001@gmail.com \
--cc=i@zenithal.me \
--cc=pve-devel@lists.proxmox.com \
--cc=w.bumiller@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