-
Notifications
You must be signed in to change notification settings - Fork 178
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
<flag value="-stdlib=libstdc++" unless="HXCPP_GCC" /> breaks on Lion #32
Comments
Is this using LLVM or GCC? Is the solution to magically set HXCPP_GCC, or is it with an old version of llvm? |
Another Lion user on IRC reported it was broken, I noticed the -m32 flag so they checked their processor and it was a 64 bit and I asked them to add haxelib run hxcpp Build.xml haxe -DGCC_OLD="1" -DHXCPP_M64="1" -DawdFile="suzanne.awd" -Dhaxe3="1" -Dhaxe_ver="3.1" -Dhxcpp_api_level="310" -DoutPutFile="summary.txt" They were running xcode 4.4.1 and I was running 4.2.1 His terminal reported gcc is Mine is I am happy to test something but I am unable to answer your question, the hxml I used for my test is online but don't think that will help. Best Justin |
his pastebin maybe useful http://pastebin.com/EVsEmkaG |
It looks like you might need HXCPP_GCC too. I guess this should be implied On Fri, Mar 21, 2014 at 1:28 PM, Justinfront notifications@github.comwrote:
|
Hugh What exactly does GCC_OLD handle, while I have 32bit processor running 64bit the other user had 64bit processor and Lion is not so old, should features missing on various mac systems not be automatically handled with try code rather than lumped together with an old flag? Best Justin |
Added |
I've run into this problem on OSX Lion as well. To be specific I was attempting to compile the native mac target using Snowkit which was failing with the following error:
It wasn't quite obvious how to fix the problem from the conversation, or at least not for someone like me who is pretty unfamiliar with Haxe. Anyway for the sake of anyone else who may run into a similar issue, here is one possible way you can fix it: In your home directory you should find a file named .hxcpp_config.xml. You might need to enable visibility of hidden files in order to see it. Open it up and add the following line somewhere between
So after the change my entire .hxcpp_config.xml file looked like this:
Compiling worked fine for me after that. Thanks anyway guys :) I would not have had a clue without this conversation. |
I think the config provides the solution. Closing this one now. |
please revert or find alternative for change
d0fc29b#diff-15e66de6f57c543a27161a3adbc163ab
Since on Lion for atleast two users it breaks compile, it results in the following compile error.
cc1plus: error: unrecognized command line option "-stdlib=libstdc++"
If I comment out line 15 in mac-toolchain.xml eg:
flag value="-stdlib=libstdc++" unless="HXCPP_GCC"
( see googlecode submitted bug for clarity )
code will now compile this was verified by another user who following my instruction and was able to use the c++ target.
The user with problems suggested we could look at Travis for mac to avoid these regression issues, but the link only seems to have 10.8.
http://docs.travis-ci.com/user/osx-ci-environment/
But maybe we can run over how travis works at wwx and I can do tests on each new hxcpp release if that is possible I have not read up on what exactly Travis is just seem to hear a lot about it.
( just reported on googlecode as well but just realized that repository is probably dead now http://code.google.com/p/hxcpp/issues/detail?id=268 )
The text was updated successfully, but these errors were encountered: