-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add GCCVER define to Toolchain. #14130
Conversation
[Experimental Bot, please feedback here] No, this PR does not meet the NuttX requirements. The provided information only includes a build error message and lacks essential details outlined in the NuttX PR requirements. Here's what's missing:
To meet the NuttX requirements, the PR needs to provide a comprehensive description of the change, its impact, and thorough testing evidence, following the template provided. |
be3d398
to
2f23220
Compare
Please make some improvements for revert back commits and make each change more valuable, rather than |
2f23220
to
b180f55
Compare
1f873eb
to
43fb27a
Compare
017dbe1
to
6333af2
Compare
please fixtheconflict, @cuiziwei1 |
cf51664
to
a862f6e
Compare
9a101c0
to
761a00a
Compare
2dd979b
to
099b3c9
Compare
099b3c9
to
f145dd2
Compare
f145dd2
to
25dc41c
Compare
4e9a9a0
to
916b0d1
Compare
Since GCCVER will also be used in the toolchain, it needs to be defined in advance. Signed-off-by: cuiziwei <[email protected]>
916b0d1
to
64f03df
Compare
Summary
We hope to find a common place to define GCCVER, so that it only needs to be specified once, which would undoubtedly be the most convenient. #14130 (comment). However, since GCCVER may be used in the Toolchain.defs of each architecture, we have to define GCCVER again.#14293 (comment)
Impact
Testing