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

Provide more reasoning behind -static-libgcc recommendation #24

Open
solvingj opened this issue Jan 7, 2020 · 0 comments
Open

Provide more reasoning behind -static-libgcc recommendation #24

solvingj opened this issue Jan 7, 2020 · 0 comments

Comments

@solvingj
Copy link

solvingj commented Jan 7, 2020

From the README

I would also recommend adding -static-libgcc -static-libstdc++ as well.

These flags seem to depend very much on the use case, and doesn't seem like something that can be "generally recommended" in a broad way. Can author please provide further commentary as to the reasoning this recommendation was made originally, and perhaps any known exceptions? Most importantly, is there some scenario in which using glibc_version_header absolutely requires these flags?

Related link showing how these flags have subtle but major impact on binary compatibility and should be considered carefully for each project:
Related link bazelbuild/bazel#2840

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

No branches or pull requests

1 participant