...and now we are with differences of apple compiled and macports compiled.
-arch is an apple specific flag... and we are using some others, I think... but you can try by using -m32 instead -arch i386 and see what happens :( change needed is in CocoaIOSConfig>>#commonCompilerFlags yeah, really long way solution will be to make the vm able to be compiled on llvm, but that's harder than it seems... also, there are a lot of small optimizations made in the assumption we use gcc as the compiler :( El 29/01/2012, a las 6:12p.m., dimitris chloupis escribió: > tried all the steps and generated sources when i try to make it fails here is > my log > > DIMITRISs-iMac:~ kilon$ cd cogvm > DIMITRISs-iMac:cogvm kilon$ cd blessed > DIMITRISs-iMac:blessed kilon$ cd build > DIMITRISs-iMac:build kilon$ ../codegen-scripts/extract-commit-info.sh > DIMITRISs-iMac:build kilon$ cmake . > -- The C compiler identification is GNU > -- The CXX compiler identification is GNU > -- Checking whether C compiler has -isysroot > -- Checking whether C compiler has -isysroot - yes > -- Checking whether C compiler supports OSX deployment target flag > -- Checking whether C compiler supports OSX deployment target flag - yes > -- Check for working C compiler: /usr/bin/gcc > -- Check for working C compiler: /usr/bin/gcc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Checking whether CXX compiler has -isysroot > -- Checking whether CXX compiler has -isysroot - yes > -- Checking whether CXX compiler supports OSX deployment target flag > -- Checking whether CXX compiler supports OSX deployment target flag - yes > -- Check for working CXX compiler: /usr/bin/c++ > -- Check for working CXX compiler: /usr/bin/c++ -- works > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > > Adding internal plugin: ADPCMCodecPlugin > Adding internal plugin: BMPReadWriterPlugin > Adding internal plugin: B2DPlugin > Adding internal plugin: BitBltPlugin > Adding internal plugin: ClipboardExtendedPlugin > Adding internal plugin: DSAPrims > Adding internal plugin: ZipPlugin > Adding internal plugin: DropPlugin > Adding internal plugin: FFTPlugin > Adding internal plugin: FilePlugin > Adding internal plugin: FloatArrayPlugin > Adding internal plugin: GeniePlugin > Adding internal plugin: HostWindowPlugin > Adding internal plugin: JPEGReadWriter2Plugin > Adding internal plugin: JPEGReaderPlugin > Adding internal plugin: Klatt > Adding internal plugin: LargeIntegers > Adding internal plugin: Matrix2x3Plugin > Adding internal plugin: MiscPrimitivePlugin > Adding internal plugin: RePlugin > Adding internal plugin: SecurityPlugin > Adding internal plugin: SocketPlugin > Adding internal plugin: SoundCodecPrims > Adding internal plugin: SoundPlugin > Adding internal plugin: StarSqueakPlugin > Adding internal plugin: SurfacePlugin > Adding internal plugin: UnixOSProcessPlugin > Adding external plugin: SqueakFFIPrims > Adding external plugin: IA32ABI > Adding external plugin: UUIDPlugin > Adding external plugin: FloatMathPlugin > Adding external plugin: AsynchFilePlugin > Adding external plugin: SerialPlugin > Adding external plugin: Mpeg3Plugin > Adding external plugin: CroquetPlugin > Adding external plugin: JoystickTabletPlugin > Adding external plugin: MIDIPlugin > Adding external plugin: B3DAcceleratorPlugin > Adding external plugin: LocalePlugin > Adding external plugin: ObjectiveCPlugin > Adding external plugin: QuicktimePlugin > Adding external plugin: TestOSAPlugin > Adding external plugin: FT2Plugin > -- Configuring done > -- Generating done > -- Build files have been written to: /Users/kilon/cogvm/blessed/build > DIMITRISs-iMac:build kilon$ make > Scanning dependencies of target UnixOSProcessPlugin > [ 1%] Building C object > UnixOSProcessPlugin/CMakeFiles/UnixOSProcessPlugin.dir/Users/kilon/cogvm/blessed/src/plugins/UnixOSProcessPlugin/UnixOSProcessPlugin.c.o > cc1: error: unrecognized command line option "-arch" > cc1: error: unrecognized command line option "-arch" > cc1: error: unrecognized command line option "-arch" > make[2]: *** > [UnixOSProcessPlugin/CMakeFiles/UnixOSProcessPlugin.dir/Users/kilon/cogvm/blessed/src/plugins/UnixOSProcessPlugin/UnixOSProcessPlugin.c.o] > Error 1 > make[1]: *** [UnixOSProcessPlugin/CMakeFiles/UnixOSProcessPlugin.dir/all] > Error 2 > make: *** [all] Error 2 > DIMITRISs-iMac:build kilon$ > > > From: Esteban Lorenzano <[email protected]> > To: [email protected]; dimitris chloupis > <[email protected]> > Sent: Sunday, 29 January 2012, 22:54 > Subject: Re: [Pharo-project] Trying to build CogVM in MacOSX 10.7 Lion > > if you have this one: i686-apple-darwin11-gcc-apple-4.2.1 > that should be the right one. > > Just create a symlink 'gcc' in /usr/bin and let's see what happens. > > > > El 29/01/2012, a las 5:50p.m., dimitris chloupis escribió: > > > it appears I was correct according to this > > > > http://ask.metafilter.com/200231/How-to-install-gcc-42-on-a-macbook-with-Xcode-42 > > > > and a gazillion other results from google . It no longer ships with > > Xcode-4.2. I assume you have upgraded from 4.1 that is why you have it. > > > > Ok I am ready to try macports but how ? > > > > > > I have several gccs in macports > > > > gcc-apple-4.2 > > > > and > > > > i686-apple-darwin11-gcc-apple-4.2.1 > > > > which one and how ? > > > > From: Esteban Lorenzano <[email protected]> > > To: dimitris chloupis <[email protected]> > > Sent: Sunday, 29 January 2012, 22:32 > > Subject: Re: [Pharo-project] Trying to build CogVM in MacOSX 10.7 Lion > > > > I really don't know... maybe Sean (who installed xcode from scratch > > recently) can confirm that. > > > > so... let's try with macports... :) > > > > best, > > Esteban > > > > El 29/01/2012, a las 5:30p.m., dimitris chloupis escribió: > > > >> in usr/bin I have i686-apple-darwin11-llvm-g++-4.2 and > >> 686-apple-darwin11-llvm-gcc-4.2. Both are symlinks that point to the > >> usr/llmv-gcc-4.2/bin and corresponding binaries. > >> > >> Dont know why, there is also a gcc binary in my home folder. Maybe I > >> accidentally moved it there before the install. > >> > >> The install was sucessful as far I can tell, there were no errors. > >> > >> as I said the only thing non llvm is in macports folder which of course is > >> not related to xcode install. I feel that I can bet serious money that the > >> new xcode comes with only llvm compilers. Maybe I am wrong. > >> > >> From: Esteban Lorenzano <[email protected]> > >> To: [email protected]; dimitris chloupis > >> <[email protected]> > >> Sent: Sunday, 29 January 2012, 22:09 > >> Subject: Re: [Pharo-project] Trying to build CogVM in MacOSX 10.7 Lion > >> > >> 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 > >> > >> who should be there... is that the case? > >> > >> > >> > >> El 29/01/2012, a las 4:51p.m., dimitris chloupis escribió: > >> > >>> there is no gcc in usr/bin at all. Afterall your first command removed > >>> the only one ;) > >>> > >>> I have reinstalled Xcode to be sure . My Xcode About box says its XCODE > >>> 4.2 build 4D199 > >>> > >>> no idea how to update cause I downloaded it via torrent, could not > >>> download from app store cause my connection is crapish and each time I > >>> disconnected it canceled my upload (no I could not resume, tried > >>> everything). So I had to install via torrent. > >>> > >>> > >>> > >>> From: Esteban Lorenzano <[email protected]> > >>> To: [email protected]; dimitris chloupis > >>> <[email protected]> > >>> Sent: Sunday, 29 January 2012, 20:49 > >>> Subject: Re: [Pharo-project] Trying to build CogVM in MacOSX 10.7 Lion > >>> > >>> There is a problem there... if you have XCode 4.2.1 (latest), you should > >>> have that one... xcode just changed the default, it did not remove the > >>> gcc, AFAIK. > >>> > >>> which versions of gcc do you have in /usr/bin? > >>> > >>> oh, btw... is ln -s, not just ln (my mistake, but both should work) > >>> > >>> (symlink macport gcc should work, but I'm fearing there is something > >>> wrong with xcode instalation, and that's probably the reason it didn't > >>> compiled the first time, so, let's be sure about that before try the port) > >>> > >>> El 29/01/2012, a las 3:40p.m., dimitris chloupis escribió: > >>> > >>>> > >>>> >> sudo rm /usr/bin/gcc > >>>> > >>>> success ! > >>>> > >>>> >> sudo ln /usr/bin/gcc-4.2 gcc > >>>> > >>>> fail ! > >>>> > >>>> no such file > >>>> > >>>> there is a gcc symlink in developer/usr/bin that point to > >>>> developer/usr/llvm-gcc-4.2/llvm-gcc-4.2 > >>>> > >>>> there is no gcc-4.2 in my Xcode folder or other folders except the gcc > >>>> folder that I installed via macports following the previous tutorial > >>>> that I have linked. Should I symlink macports gcc-4.2 ? > >>>> > >>>> Xcode is by default isntalled in the Developer folder > >>>> > >>>> I am open to suggestions and thanks for helping me. > >>>> > >>>> > >>>> > >>> > >>> > >>> > >> > >> > >> > > > > > > > > >
