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

USERSPACE and CMAKE_LINKER_GENERATOR #85277

Open
RobinKastberg opened this issue Feb 6, 2025 · 0 comments
Open

USERSPACE and CMAKE_LINKER_GENERATOR #85277

RobinKastberg opened this issue Feb 6, 2025 · 0 comments
Assignees
Labels
area: Build System area: Userspace Userspace bug The issue is a bug, or the PR is fixing a bug

Comments

@RobinKastberg
Copy link
Contributor

To Reproduce
Try to build any application/test with CONFIG_USERSPACE=y and CONFIG_CMAKE_LINKER_GENERATOR=y

Expected behavior
Working

Impact
This will cause problems if you want to use USERSPACE together with armclang or IAR toolchain.

Logs and console output

user@b7f43aa2a597:/workdir/zephyr$ scripts/twister -T samples/hello_world/ -x CMAKE_LINKER_GENERATOR=y -x CONFIG_USERSPACE=y
Renaming output directory to /workdir/zephyr/twister-out.1
INFO    - Using Ninja..
INFO    - Zephyr version: v4.0.0-4635-g2fc39ec3f35a
INFO    - Using 'zephyr' toolchain.

Currently, we (IAR) are working with a two pronged approach

  1. is getting tests: kconfig: cmake: Disable USERSPACE when using LINKER_GENERATOR #85075 into main. This will make IAR twister tests go green without spurious failures because of this.
  2. is getting Make CONFIG_USERSPACE=y and CONFIG_CMAKE_LINKER_GENERATOR=y work together #85241 into main. This will make CMAKE_LINKER_GENERATOR+USERSPACE work for ld, and the workaround above can be reverted/closed (or made more toolchain specific).
@RobinKastberg RobinKastberg added the bug The issue is a bug, or the PR is fixing a bug label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Build System area: Userspace Userspace bug The issue is a bug, or the PR is fixing a bug
Projects
None yet
Development

No branches or pull requests

3 participants