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

Clang can't use libgcc from a gcc compiled with --disable-shared #32805

Open
llvmbot opened this issue Jun 14, 2017 · 1 comment
Open

Clang can't use libgcc from a gcc compiled with --disable-shared #32805

llvmbot opened this issue Jun 14, 2017 · 1 comment
Labels
bugzilla Issues migrated from bugzilla clang:driver 'clang' and 'clang++' user-facing binaries. Not 'clang-cl'

Comments

@llvmbot
Copy link
Member

llvmbot commented Jun 14, 2017

Bugzilla Link 33458
Version unspecified
OS All
Reporter LLVM Bugzilla Contributor

Extended Description

In a regular gcc installation there is libgcc.a, libgcc_s.so and
libgcc_eh.a.

In a regular link libgcc.a and libgcc_s.so are used.
In a static link libgcc.a and libgcc_eh.a are used.

But when gcc is built with --disable-shared, there is no
libgcc_eh.a. Everything is in libgcc.a.

This means that clang has to know if the gcc installation is static or
not. Currently it assumes it is not.

@lf-
Copy link
Contributor

lf- commented Sep 18, 2024

This is still the case against Clang 17.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugzilla Issues migrated from bugzilla clang:driver 'clang' and 'clang++' user-facing binaries. Not 'clang-cl'
Projects
None yet
Development

No branches or pull requests

2 participants