Hans Mackowiak

No i mean i can build rwx with or without --stdlib, both of them does work BUT if i start the program, AND wxwidgets does not have the SAME stdlib...

checking for "HAVE_TR1_TYPE_TRAITS" and "HAVE_TYPE_TRAITS" is not check enough for libc++ but for c++11 (libc++ can be build without c++11 too) but HAVE_ABI_FORCEDUNWIND is something that does not exist on...

no, adding libc++ does not automaticlly enable c++11, thats extra! did you test it if that latest changes does works for you?

that is what i already told you about, but you did say once that HAVE_TR1_TYPE_TRAITS might be enough to check between libstdc++ and libc++ which is not. can you test...

i will not add have_std_header because my code doesnt need checks for c+11 same why $CFLAGS += " -std=c++11 -stdlib=libc++ -nostdinc++" will not added pkg_conf will also not added because...

like i said in the other ticket before, update your software (newer gcc or newer clang) and then recompile ruby and wxwidgets again wxwidgets should not use any c+11 features...

i currently cant test it on OSX now, but i tested it local on my machine and it did work with clang too (it did show warnings but thats ok)...

what is your clang version wxwidgets is build against? if its some hidden gcc42 then its a broken version (it was still broken the last time i checked) what is...

your ruby seems still be build against gcc then clang try to install a clang version with rvm using --clang while installing the ruby version

the problem is more that it might try to find the wrong folder then maybe the detection in wx is broken but not in my program is your ruby really...