I am afraid that wont work XCODE no longer comes with any gcc included besides llvm-gcc (I am not near my mac to try this but I am pretty sure it will fail). Apple has abandoned gcc completely and it wont be included again in XCODE as far as I have ready from the several websites.
Last gcc was included was XCODE 4.1. If you are like me a user with a clean install of Lion and XCODE 4.2 you are out of lack. By the way you are not the only one open source project to have this issue , seems all open source project are faced with the same issue. I am a noob with this whole thing but I think that on macos at least if you still want to depend on XCODE llvm is an one way street. ________________________________ From: Camillo Bruni <camillo.br...@inria.fr> To: Pharo-project@lists.gforge.inria.fr Sent: Monday, 30 January 2012, 4:34 Subject: Re: [Pharo-project] Trying to build CogVM in MacOSX 10.7 Lion I extended the HOWTOBUILD in the blessed repository. For me cd build export CC='/usr/bin/gcc-4.2' # as of 10.7 llvm is the incompatible default compiler export MACOSX_DEPLOYMENT_TARGET=10.5 cmake . make worked. And yeah, I wouldn't symlink it either :) too bad that we can't use clang/llvm yet for the compilation. The error handling is so much better than in gcc :P best cami On 2012-01-29, at 22:06, Esteban Lorenzano wrote: > maybe, but he can restore default gcc after trying. I asked for removing a > symlink, not the llvm compiler it self. > Right now I do not have a better/faster way to doit... and he needs to > compile his vm, so... > > > El 29/01/2012, a las 6:00p.m., Stefan Marr escribió: > >> >> On 29 Jan 2012, at 21:09, Esteban Lorenzano wrote: >> >>> he... connection problems... yeah, I know a lot about them :) >>> >>> well... after a successful install, I *think* you should have gcc and >>> gcc-4.2... last one is also a symlink who points to: >>> >>> /usr/bin/i686-apple-darwin11-gcc-4.2.1 >> >> We have seen GCC 4.2 disappearing after Lion upgrades and Xcode 4.2 installs. >> >> And Esteban, I do not think that changing the systems default compiler just >> for a single program can be the recommended practice. >> >> "sudo rm /usr/bin/gcc" is certainly only the very last resort. >> It should not be advertised if there are other ways to use a supported >> compiler. >> Camillo mentioned that setting the CC environment variables correctly worked >> for him. >> >> >> ... sudo - With great power comes great responsibility ... >> >> Best regards >> Stefan >> >> -- >> Stefan Marr >> Software Languages Lab >> Vrije Universiteit Brussel >> Pleinlaan 2 / B-1050 Brussels / Belgium >> http://soft.vub.ac.be/~smarr >> Phone: +32 2 629 2974 >> Fax: +32 2 629 3525 >> >> > >
