On Wed Dec 03 11:56:40 2008, coke wrote: > On Sat Aug 04 06:42:44 2007, [email protected] wrote: > > chromatic wrote: > > > > > > > > Ahh, this patch fixes things for me. My gcc is also available as cc > > (and I'm > > > using ccache), so checking that it matches the literal string 'gcc' > > doesn't > > > work. Explicitly checking that it has a GCC version number works > > better. > > > > > > > Unfortunately, it did not improve things for me. > > > > -rw-r--r-- 1 jimk jimk 71898 Jul 15 10:30 15.07.2007.make.txt > > -rw-r--r-- 1 jimk jimk 73181 Jul 22 21:17 21.07.2007.make.txt > > -rw-r--r-- 1 jimk jimk 7167507 Aug 3 21:43 03.08.2007.make.txt > > -rw-r--r-- 1 jimk jimk 7167507 Aug 4 07:24 04.08.2007.make.txt > > > > Note that I have to call Configure.pl in the following manner: > > > > #!/bin/sh > > CC="/usr/bin/gcc-3.3" > > CX="/usr/bin/g++-3.3" > > /usr/local/bin/perl Configure.pl --cc="$CC" --cxx="$CX" --link="$CX" \ > > --ld="$CX" --without-icu --without-gmp \ > > $@ > > > > A few notes: > > - The patch on this ticket doesn't apply anymore. > - I can't even run configure with gcc 3.3 on my OSX 10.4.11 box, either > with a straight gcc_select 3.3 or with the explicit settings listed > here. I'm not sure 3.3 is meant to work on OS X/intel, though. > > It is tempting to drop 3.3 support for now and concentrate on 4.x for > the parrot 1.0 release. A pointer to a gcc version/OS X version/CPU arch > matrix would be nice, if anyone can find one. > > If anyone is successfully running gcc3.x on OS X, can you duplicate the > report?
If more warnings surface, please document them at https://trac.parrot.org/parrot/wiki/BuildWarnings. Thanks. -- Will "Coke" Coleda _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
