Created attachment 685446 [details] emerge -pqv Getting this error during compilation. This machine is a clang+llvm box, but I have reproduced this error with gcc as well.
Created attachment 685449 [details] emerge --info
Created attachment 685452 [details] build.log
I can only reproduce with -stdlib=libc++, otherwise clang works fine. gcc is fine on my end too, but I don't know what you've used with it.
(In reply to Ionen Wolkens from comment #3) > I can only reproduce with -stdlib=libc++, otherwise clang works fine. > > gcc is fine on my end too, but I don't know what you've used with it. Looks like you're right. If libc++ support is out of scope I'm OK with closing this, but otherwise a fix for it would be nice. It's not a dealbreaker though, as I've got the necessary env vars to build it with libstdc++, and it runs fine anyways.
Created attachment 685950 [details, diff] fix building with libc++ The issue is caused by `using namespace std;`
Hmmm, would option(USE_LIBC++ "Use libc++ instead of libstdc++" ${APPLE}) if(USE_LIBC++) set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -stdlib=libc++") be of any help with this?
(In reply to 12101111 from comment #5) > Created attachment 685950 [details, diff] [details, diff] > fix building with libc++ > > The issue is caused by `using namespace std;` I can confirm this patch fixed the issue. Would it be appropriate to apply this patch conditionally in the ebuild, perhaps with a USE=libcxx? (In reply to Chiitoo from comment #6) > Hmmm, would > > option(USE_LIBC++ "Use libc++ instead of libstdc++" ${APPLE}) > > if(USE_LIBC++) > set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -stdlib=libc++") > > be of any help with this? I think if a USE=libcxx existed, this should be enabled by that flag. All of this might be a little too much to ask. I've no idea if building with libc++ is officially supported in Gentoo or not, but I have it working on 4 different systems for the most part.
obs-studio 27.2.0 builds fine now, no user patch necessary. I've no problem closing this bug unless there's some other reason to keep it open.
Heh, I was just about to close with the following comment. :] Looks like the fix got in on 27.2? Let us know if there's still something for us to do here. Thanks!
