Skip to content
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

Profiles contain RTX symbol (bare metal error) #11565

Closed
0xc0170 opened this issue Sep 25, 2019 · 3 comments · Fixed by #11699
Closed

Profiles contain RTX symbol (bare metal error) #11565

0xc0170 opened this issue Sep 25, 2019 · 3 comments · Fixed by #11699

Comments

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 25, 2019

Description

This PR #8887 added debug awareness - linker flag addition keep a section that is RTX specific. This introduced a warning to the baremetal build and mbed 2 - there is no os_cb_sections.

Reading this comment: https://github.com/ARMmbed/mbed-os/pull/8887/files#r243106755 , is this still needed?

One interesting fact about this warning: users think this warning causes build failing in the online compiler. There are so many reports about this, see https://os.mbed.com/questions/85360/Error-Warning-L6320W-ignoring-keep-comma/#answer16979 , https://os.mbed.com/questions/86252/Cant-Compile-Error-Warning-L6320W-Ignori/ and others. The real error there is not always shown, leads a user to believe this warning is actually an error and causing their apps not to build.

Issue request type

[ ] Question
[ ] Enhancement
[X] Bug
@0xc0170
Copy link
Contributor Author

0xc0170 commented Sep 25, 2019

cc @ARMmbed/mbed-os-core

@ciarmcom
Copy link
Member

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-1818

@evedon
Copy link
Contributor

evedon commented Sep 26, 2019

We should be able to work on this shortly as we are looking at changing linker options for bare metal.
cc @rajkan01

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

Successfully merging a pull request may close this issue.

3 participants