Open ChrisDenton opened 3 months ago
@semarie, does powerpc-unknown-openbsd
have std support? Does it support running rustc on the powerpc?
Regarding powerpc-unknown-openbsd
, currently there is no support on OpenBSD by any OpenBSD developers. It was added in rust by @Yn0ga in https://github.com/rust-lang/rust/pull/82733, and I am unaware if it is functional or not.
So I would keep no std support, and no rustc binary.
Thanks!
@Yn0ga would you be ok being listed as the maintainer for the powerpc-unknown-openbsd
target?
Does anyone know who maintains the freebsd targets? @devnexen, I think you've been actively contributing for freebsd? Do you know which targets have std support? Do any have host tools support? Currently we have 3 freebsd targets with missing information:
powerpc64le-unknown-freebsd
powerpc-unknown-freebsd
riscv64gc-unknown-freebsd
for FreeBSD, I would ping @asomers , @MikaelUrankar or @dankm (the commiters list in freebsd ports tree could found from https://github.com/freebsd/freebsd-ports/commits/main/lang/rust). the mail contact is rust@FreeBSD.org
.
@ChrisDenton I don't work on rustc itself. But does the fact that I can do cargo check -Zbuild-std
successfully for all three targets mean that they do have std support? I think it does.
Thanks @asomers! Successfully checking std is definitely a good sign. Though for maintenance purposes it's also good to know there's someone to willing to do maintenance should things break, Could someone from FreeBSD fill out contact information? E.g. we have a page for OpenBSD and NetBSD. If you'd like I can make a PR, I just need to know what to write.
i think it makes sense to wait for # #121051 with this effort. it will make it easier to track and will avoid duplicated effort of first adding docs and then migrating them. if you want to help out getting that PR merged, ping me somewhere
Yes @ChrisDenton you can put me down. Also, use rust@FreeBSD.org as a fallback.
Chris,
Thanks for reaching out. Unfortunately I'm really far from OpenBSD and rust these days (and from computing in general) so I'm afraid I won't be a really good fit for the role.
Sorry about the let down. Take Care.
-------- Message d'origine -------- Le 14/06/2024 07:50, Chris Denton a écrit :
Thanks!
@.***(https://github.com/Yn0ga) would you be ok being listed as the maintainer for the target?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
Yes @ChrisDenton you can put me down. Also, use rust@FreeBSD.org as a fallback.
Thanks!
Chris, Thanks for reaching out. Unfortunately I'm really far from OpenBSD and rust these days (and from computing in general) so I'm afraid I won't be a really good fit for the role. Sorry about the let down. Take Care.
No worries! Thanks for responding so quickly.
https://github.com/rust-lang/rust/pull/126192 will add target information for all Redox OS targets (both tier 2 and tier 3).
All 6 vxworks targets platform support information is updated with pr #128431
Except for powerpc64-wrs-vxworks
?
Except for
powerpc64-wrs-vxworks
?
We're not actively working on rust for VxWorks PowerPC targets. They are not built or shipped with the current VxWorks workbench.
I missed powerpc64-wrs-vxworks
during that pr.
commit 1e3ea29 completes platform support documentation for VxWorks.
There are a number of tier 3 targets with missing support information on the Platform Support page. Let's fix that!
If you're maintain one or more of these targets can you answer the following questions:
no_std
?You can either answer here or send a PR to update the Platform Support page.
I'll start trying to ping maintainers as I figure out who they are.