Skip to content

picolibc: Enable dual-mode picolibc builds #819

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

Closed
wants to merge 2 commits into from

Conversation

keith-packard
Copy link
Contributor

This provides both minsize and release versions of picolibc in the SDK, allowing users to select between them while building their application.

This provides both minsize and release versions of picolibc in the SDK,
allowing users to select between them while building their application.

Signed-off-by: Keith Packard <[email protected]>
In release builds, several targets would get both asm and C versions
of strchr included, which is a fatal picolibc build error. Pull
in the fix for that.

Signed-off-by: Keith Packard <[email protected]>
@keith-packard
Copy link
Contributor Author

Looks like this increased the linux x86 toolchain from 1.59GB to 1.66GB?

@keith-packard keith-packard added the DNM DO NOT MERGE label Oct 12, 2024
@keith-packard
Copy link
Contributor Author

GCC has a bug which breaks Zephyr's use case for 'dual' mode. Working on a fix.

@stephanosio
Copy link
Member

@keith-packard Is this still relevant?

@stephanosio
Copy link
Member

  • Closing as stale. Please re-open if this is still relevant.

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

Successfully merging this pull request may close these issues.

2 participants