-
Notifications
You must be signed in to change notification settings - Fork 229
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
Build error due to incompatibility with _GLIBCXX_USE_CXX11_ABI=0 #708
Comments
The issue is on my side; there's a mismatch between the system glibc (alwayx cxx11 string ABI) and what I'm building. EDIT: actually, scratch that, it looks like my glibc does support both string ABIs:
|
Hi @maleadt |
Building with |
@maleadt could you provide repro steps how you setup I cannot reproduce the issue on my side |
For redistribution purposes, I'm building compute_runtime (as well as dependencies like libigc) both using _GLIBCXX_USE_CXX11_ABI=0 (cxx03 string ABI) and _GLIBCXX_USE_CXX11_ABI=1 (cxx11 string ABI), using a compiler wrapper script that sets this flag as late as possible.
Since 18c25e5, our cxx03 build has mysteriously broken, with
ocloc
segfaulting during compilation of builtins:Looking at GDB, this indeed seems related to the string ABI:
... but I haven't been able to come up with an MWE. I'm not sure yet how limiting the list of symbols exported from libocloc could affect this; looking at the objects and libraries in the build I don't see any
std::__cxx11::basic_string
signatures. It's possible or even likely I'm doing something wrong, but would appreciate any thoughts here.The text was updated successfully, but these errors were encountered: