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

Properly handle newlib configuration flags #984

Merged
merged 1 commit into from
Sep 26, 2018

Conversation

slash3g
Copy link
Contributor

@slash3g slash3g commented Jun 11, 2018

Some configuration-time flags for newlib are prefixed with "newlib-", i.e. we need to pass --enable-newlib-FEATURE to the configure script. Unfortunately, newlib.sh do not add this prefix when enabling the features atexit-dynamic-alloc, reent-small, multithread, and unbuf-stream-opt. Thus, enabling these options in crosstool-ng's config has no effect on the generated libc.
This patch fixes this bug.

@antmak
Copy link
Contributor

antmak commented Jun 12, 2018

Useful, thanks!

But i'm not sure that this is true for all supported versions of newlib. Do you use newlib 2.5.0.20171222 or 3.0.0.20180226 ?

@slash3g
Copy link
Contributor Author

slash3g commented Jun 12, 2018

I'm currently using newlib 3.0.0.20180226; however, git shows no changes in newlib's configure.in from 2.5.0.20171222, so I think it is safe to assume that the configuration flags did not change between these two versions.

@antmak
Copy link
Contributor

antmak commented Jun 12, 2018

A good fix. Just notice that I've looked at full history of newlib/configure.in . I found all old versions of newlib had a *newlib-* names as in your PR

@slash3g
Copy link
Contributor Author

slash3g commented Sep 2, 2018

Any news on if/when this pull request will be merged? Should I improve it in any way to make it mergeable?

@stilor stilor merged commit b82b8ad into crosstool-ng:master Sep 26, 2018
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.

None yet

3 participants