QNX target renaming#2418
Closed
jonathanpallant wants to merge 12 commits into
Closed
Conversation
- aarch64-unknown-nto-qnx800 becomes simply aarch64-unknown-qnx - x86_64-pc-nto-qnx800 becomes simply x86_64-pc-qnx - references to QNX OS and QNX Neutrino RTOS are replaced with QNX SDP for uniformity - various nto_qnx modules are named to qnx_sdp to match the above The new target names are more consistent with those used by the QNX SDP 8.0 toolchain, and reflect a level on ongoing API stability similar to that for macOS and Linux (which simply have minimum supported versions record for their targets).
Closed
Contributor
|
bors try |
Contributor
tryBuild failed: |
jonathanpallant
commented
Jun 26, 2026
jonathanpallant
commented
Jun 26, 2026
Use QNX SDP 8.0 when talking about the product in general, leaving 8.0.0 Build 141 as the specific when talking about qualifiied uses and/or toolchain installation for Ferrocene staff.
QNX 8.0 is not a thing, and 8.0.0 is over-precise. The details can clarify which release of 8.0 we test against.
QNX SDP is the build environment and is more useful to note here than QNX Neutrino or QNX OS, which are the run-time environment.
jonathanpallant
commented
Jun 26, 2026
| -installPackage com.qnx.qnx800.host.linux.x86_64=$QNX_LINUX_HOST_VERSION \ | ||
| -installPackage com.qnx.qnx800.target.qemuvirt/0.2.1.00087T202507241124L \ | ||
| -installPackage com.qnx.qnx800.target.driver.virtio.devc/0.1.1.00011T202411230100L \ | ||
| -installPackage com.qnx.qnx800.patchset805/8.0.5.00390T202606231321L \ |
Contributor
Author
There was a problem hiding this comment.
If we install this patch set, do the notes about which version we qualified need changing on the target pages as well?
ping @japaric
Contributor
Author
|
bors try |
Contributor
tryBuild failed: |
Contributor
|
i believe we've decided this should go upstream first before we merge it here. i'm going to unsubscribe from notifications, ping me if you need anything. |
Contributor
Author
|
Yes. Upstream PR: rust-lang/rust#158449 |
Merged
Contributor
|
closing in favor of #2439 |
bors-ferrocene Bot
added a commit
that referenced
this pull request
Jul 10, 2026
2422: update QNX scripts to work with QEMU built from source r=jyn514 a=japaric `qemu-system-$ARCH -netdev bridge,(..)` uses the qemu-bridge-helper script that was installed with `qemu-system-$ARCH`. However, to set up the bridge network in the QNX scripts, we are using the qemu-bridge-helper of the system installed QEMU. When using a QEMU built from source, we have seen the VM fail to initialize due to a different version of qemu-bridge-helper being used to set up the network bridge. To ensure the right qemu-bridge-helper is using in the QNX script, we search for it using the absolute path of the `qemu-system-$ARCH` as the reference, instead of assuming it'll be in `/usr` as that only works when the system installed QEMU is used. 2439: QNX target renaming r=jyn514 a=japaric **NOTE** depends and includes PR #2454 This is a rebased version of #2418 now that rust-lang/rust#158449 has been merged. the first six commits in this PR are a cherry picks the commits in rust-lang/rust#158449. the rest of commits are a cherry pick of #2418. note that commit [fix rustdoc-html tests](1483680) has been dropped because it became unnecessary with upstream commit rust-lang/rust@4eec7f5 --- - `aarch64-unknown-nto-qnx800` becomes simply `aarch64-unknown-qnx` - `x86_64-pc-nto-qnx800` becomes simply `x86_64-pc-qnx` - references to QNX OS and QNX Neutrino RTOS are replaced with QNX SDP (Software Development Platform) for uniformity - various `nto_qnx` modules are renamed to `qnx_sdp` to match the above The new target names are more consistent with those used by the QNX SDP 8.0 toolchain, and reflect a level on ongoing API stability similar to that for macOS and Linux (which simply have minimum supported versions record for their targets). The new target names also match what the copy of `clang` shipped in the QNX Desktop Image (part of QNX SDP 8.0) self reports as (that is, `clang` running self-hosted *on* QNX). 2448: Remove gcc submodule and mark GCC codegen backend as unsupported r=fs-rachel a=fs-rachel 2451: Sync dependencies between linkchecker and dist tarball r=jyn514 a=fs-rachel Co-authored-by: Jorge Aparicio <[email protected]> Co-authored-by: Jonathan Pallant <[email protected]> Co-authored-by: Rachel Barker <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Testing out QNX target renaming. There's an equivalent of this PR that should go upstream first - this is just to test some things.
aarch64-unknown-nto-qnx800becomes simplyaarch64-unknown-qnxx86_64-pc-nto-qnx800becomes simplyx86_64-pc-qnxnto_qnxmodules are renamed toqnx_sdpto match the aboveThe new target names are more consistent with those used by the QNX SDP 8.0 toolchain, and reflect a level on ongoing API stability similar to that for macOS and Linux (which simply have minimum supported versions record for their targets). The new target names also match what the copy of
clangshipped in the QNX Desktop Image (part of QNX SDP 8.0) self reports as (that is,clangrunning self-hosted on QNX).