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
ustring::string() returns empty string when using the new C++11 ABI #1174
Comments
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this issue
Jun 26, 2015
This makes it work (and adds a test). We still need to return and do something more clever for that case. I'll need to install gcc 5.1 first to see how the internals work. But in the mean time, at least this will unbreak things for people already on gcc 5.1. Fixes AcademySoftwareFoundation#1174
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this issue
Jun 26, 2015
This makes it work (and adds a test). We still need to return and do something more clever for that case. I'll need to install gcc 5.1 first to see how the internals work. But in the mean time, at least this will unbreak things for people already on gcc 5.1. Fixes AcademySoftwareFoundation#1174
Can you test this workaround? #1176 |
Seems to work, thanks! Please note that most (if not all) Linux distros configure GCC 5.1 to use the old ABI (using |
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this issue
Jun 26, 2015
This makes it work (and adds a test). We still need to return and do something more clever for that case. I'll need to install gcc 5.1 first to see how the internals work. But in the mean time, at least this will unbreak things for people already on gcc 5.1. Fixes AcademySoftwareFoundation#1174
SomeoneSerge
pushed a commit
to SomeoneSerge/arch-community-packages
that referenced
this issue
Sep 4, 2016
AcademySoftwareFoundation/OpenImageIO#1174 git-svn-id: file:///srv/repos/svn-community/svn@135909 9fca08f4-af9d-4005-b8df-a31f2cc04f65
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed that when using GCC 5.1 with the new libstdc++ ABI enabled,
oslc foo.osl
(from OpenShadingLanguage) would choose.oso
as the output filename instead offoo.oso
.oslc uses
shader_decl()->shadername().string() + ".oso"
as the default output filename if one is not provided via the-o
option. Further testing indicates that OpenImageIO'sustring::string()
method is broken and returns an empty string on the new C++11 ABI.Bellow is an example test program and GDB backtrace that show the issue.
The text was updated successfully, but these errors were encountered: