Skip to content

Conversation

@pawelrutkaq
Copy link

@pawelrutkaq pawelrutkaq commented Oct 29, 2025

This PR adds support for QNX8 since this target is supported from rustc 1.85.0 and from cfg-ext 0.19.0

@pawelrutkaq pawelrutkaq force-pushed the pawelrutkaq_add_qnx8_support branch from 45b3090 to 5a60bf7 Compare October 30, 2025 15:23
@pawelrutkaq
Copy link
Author

@krasimirgg maybe You could look here and tell me if this is right direction and we can continue or there are some other things one needs to do ?

@pawelrutkaq
Copy link
Author

Is there a way to run failing workflow locally ? https://buildkite.com/bazel/rules-rust-rustlang/builds/15966/steps/canvas?sid=019a35b7-e271-4132-b386-adbd15454eca It seems it used rustc 1.85.0 where I understood it shall at least 1.86.0

@pawelrutkaq pawelrutkaq force-pushed the pawelrutkaq_add_qnx8_support branch from 5a60bf7 to c55b209 Compare November 26, 2025 11:08
@pawelrutkaq pawelrutkaq mentioned this pull request Nov 28, 2025

_T3_PLATFORM_TRIPLES = {
"aarch64-unknown-nto-qnx710": _support(std = True, host_tools = False),
"aarch64-unknown-nto-qnx800": _support(std = True, host_tools = False),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the difference between aarch64-unknown-nto-qnx710 and aarch64-unknown-nto-qnx800? Can these be matched as different platforms? Or is this a similar issue to bazelbuild/platforms#38 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants