tests run_shell_test and run_exec_anatomy on OS X Mavericks

[vguerra]

Hi @rizsotto ... I was trying to install Bear on my computer and building goes without errors but when trying to run make check 2 of the 5 test cases fail for me: run_shell_test and run_exec_anatomy.

run_shell_test:
In this case the compilation database file is generated but I see that there are duplicated entries. It has 12 entries and according to the ./test/end-to-end/compile.sh script it should have only 4. Looks like each call to g++ ends up generating two more. Here you have the json file in case you want to have a look at it:
http://pastebin.com/M8p49t9j

run_exec_anatomy:
Again, the compilation database generated by the test case seems to be different from the one expected (/test/exec_anatomy/expected.json). And here the json file for this case:
http://pastebin.com/Evb2bzfv

I am running on:
Darwin tlf32.wu-wien.ac.at 13.1.0 Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64

[rizsotto]

hi @vguerra ,

thanks for the report. i did looked into the pastebin outputs. (can't reproduce those on my machine) it looks to me that you got compiler wrappers installed and used on your computer.

g++ is calling /Applications/Xcode.app/Contents/Developer/usr/bin/g++ which is calling /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++. and cc is calling /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang.

are these files (execpt the clang instances) wrappers? can you also show it somehow to me?

bear is already filtering compilers. you could take a look at the bear.conf file. (currently it allows those well known compiler names from any location.) maybe you should replace those with something like /usr/bin/clang(\\+\\+)$.

ps.: did you try to install bear from homebrew?

[vguerra]

thank you for the quick response!

Unfortunately g++ and cc are binaries as well. But dtruss showed that effectively those are simply wrappers to /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ and /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang respectively.

Yeah.. I spotted that bear.conf file, I'll try to add the corresponding entries in order to filter out the wrappers.

No.. I cloned the repo and built it my self. Should I try to install from homebrew?

Thanks again @rizsotto.

[rizsotto]

okay, so i could read the log properly. ;) please let me know if i can help you more. now i would close this ticket, but can reopen if we need to change on Bear.

about homebrew, i just wanted to know how it behaves in your environment. probably needs the config adjustment as well, but maybe the building process also behaves funny.

[vguerra]

Sorry I didn't comment earlier.

I just wanted to confirm that modifying the compilers accepted from the bear.conf file allowed me to run the tests with out errors. I basically removed the regular expressions that would match the clang* compilers.

[rizsotto]

no problem, and thank you for the report. i added your finding into the readme file yesterday. hope it will help others as well.