From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Warner Losh <imp@bsdimp.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Hanna Reitz" <hreitz@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
pkg-qemu-devel@lists.alioth.debian.org,
"Michael Tokarev" <mjt@tls.msk.ru>,
ncopa@alpinelinux.org, bofh@freebsd.org, emulation@freebsd.org,
virtualization@gentoo.org, dilfridge@gentoo.org, hi@alyssa.is,
edolstra+nixpkgs@gmail.com, brad@comstyle.com,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
dvzrv@archlinux.org, anatol.pomozov@gmail.com,
"Miroslav Rezanina" <mrezanin@redhat.com>
Subject: Re: Rust BoF and maintainer minutes and planning the roadmap to Rust
Date: Thu, 3 Oct 2024 11:58:27 +0100 [thread overview]
Message-ID: <Zv540yb8V1sSnZP3@redhat.com> (raw)
In-Reply-To: <CANCZdfoU4stiEDJKOUEpU-ek_tOBHe0rBH3G9S2Wymc8jHKzCQ@mail.gmail.com>
On Thu, Oct 03, 2024 at 02:53:08AM -0600, Warner Losh wrote:
> commitment by the Rust community is troubling. Even more troubling because
> rust still uses the old FreeBSD 11 compat syscalls, despite upgraded
> being available for years at this point (though maybe this info has changed
> in the last month or two, the years long delay in moving off the interfaces
> that the FreeBSD project obsoleted about 8 years ago is troubling on its
> own).
Is this problem resolved by this change updating to FreeBSD 12 ABI:
https://github.com/rust-lang/libc/pull/3434
Or is there more beyond that which remains an issue ?
Also what's the best source of truth about Rust support in FreeBSD
eg I see this:
https://wiki.freebsd.org/Rust
Reports i386, amd64, armv6, armv7, aarch64, power64, power64le
and riscv64
and then this
https://www.freshports.org/lang/rust
but doesn't say anything about riscv64, and armv6/i386 is listed as
"N/A" for FreeBSD 15 - are those arches no longer supported in 15 ?
power64le is outdated there compared to other arches
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-10-03 10:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 14:23 Rust BoF and maintainer minutes and planning the roadmap to Rust Alex Bennée
2024-09-26 15:03 ` Stefan Hajnoczi
2024-09-30 10:23 ` Alex Bennée
2024-09-30 10:51 ` Stefan Hajnoczi
2024-09-26 16:43 ` Daniel P. Berrangé
2024-09-27 7:28 ` Markus Armbruster
2024-10-22 11:55 ` Paolo Bonzini
2024-09-27 2:06 ` Junjie Mao
2024-10-03 8:53 ` Warner Losh
2024-10-03 8:55 ` Warner Losh
2024-10-03 9:56 ` Alex Bennée
2024-10-03 11:29 ` Michael Tokarev
2024-10-14 22:45 ` Warner Losh
2024-10-15 7:23 ` Alex Bennée
2024-10-03 9:53 ` Daniel P. Berrangé
2024-10-03 10:04 ` Warner Losh
2024-10-03 10:58 ` Daniel P. Berrangé [this message]
2024-10-22 11:10 ` Paolo Bonzini
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=Zv540yb8V1sSnZP3@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=anatol.pomozov@gmail.com \
--cc=armbru@redhat.com \
--cc=bofh@freebsd.org \
--cc=brad@comstyle.com \
--cc=dilfridge@gentoo.org \
--cc=dvzrv@archlinux.org \
--cc=edolstra+nixpkgs@gmail.com \
--cc=emulation@freebsd.org \
--cc=hi@alyssa.is \
--cc=hreitz@redhat.com \
--cc=imp@bsdimp.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=mjt@tls.msk.ru \
--cc=mrezanin@redhat.com \
--cc=ncopa@alpinelinux.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pkg-qemu-devel@lists.alioth.debian.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=virtualization@gentoo.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 NNTP newsgroup(s).