Comment 1 by Alex TP Quick, Oct 11, 2012
Same problem here... can't compile Chameleon with latest Xcode version due to libcc_kext.a :(
Comment 2 by zenith432, Oct 12, 2012
Here's a workaround I used - Downloaded Command Line Tools from August 2012. - Extracted older libcc_kext.a with Pacifist. - put the older libcc_kext.a into i386/boot2 - Edited i386/boots/Makefile and changed the path to libcc_kext.a (3 locations) to take it locally from i386/boot2. After this, build succeeded (with latest Command Line Tools from October 2012.)
Comment 3 by Alex TP Quick, Oct 13, 2012
Thanks for the hint! If anyone need it, here's the file
- libcc_kext.a.zip - 30.14 kB
Comment 4 by Richard Tan, Oct 14, 2012
Hi All... To All the lazy ones....;) Below is .zip file of two command(including a Xcode 4.5.x Workaround)scripts i've made for downloading and compiling chameleon source (but only for main & EmaC Trunks) to produce the basic lifesaver i386 folder & pkg file. Hope it works for you and feel to to modify them to fit your needs...
Comment 5 by Richard Tan, Oct 14, 2012
Ooops...I forgot to say that the 'Chameleon Compile.command' script that came with the 'Xcode 4.4.X & Below-Script' folder in the zip file can be used for day to day needs when the Xcode 4.5.x problems are resolved..;)
Comment 6 by Cosmosis Jones, Oct 16, 2012
cc1: error: invalid option argument '-Oz' cc1: error: unrecognized command line option "-arch" cc1: error: unrecognized command line option "-Wmost" what did you do to workaround those?
Comment 7 by zenith432, Oct 16, 2012
Those don't happen to me. Either your build environment is screwed up or the Makefiles are malformed. The errors mention valid command-line options to gcc.
Comment 8 by Cosmosis Jones, Oct 16, 2012
lol i used the script which downloaded new source/etc.. probably need to port select gcc.. sry
Comment 9 by Cosmosis Jones, Oct 16, 2012
also was thinking of just integrating this http://nawcom.com/osx86/chameleon-macports.diff and then making people use apple-gcc42.. dont' know yet
Sign in to reply to this comment.
Reported by Richard Tan, Oct 4, 2012