Thread overview
Mac GCC Compiler crashes compiling GDC
Nov 08, 2005
David Friedman
November 08, 2005
Nope, doing the vanilla build didn't work for me.
Mac OS X 10.4.3 "Tiger", Xcode 2.1 ("gcc-5026.1")

Selected outputs from the build: (with GCC 4.0.2)


c++   -g -O2  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes     -DHAVE_CONFIG_H -I. -Id -I../../gcc
-I../../gcc/d -I../../gcc/../include -I./../intl
-I../../gcc/../libcpp/include     -I. -Id -I../../gcc -I../../gcc/d
-I../../gcc/../include -I./../intl -I../../gcc/../libcpp/include
-I../../gcc/d -I../../gcc/d/dmd -Id -D_GNU_SOURCE=1
-DD_PHOBOS_DIR=\"/opt/gdc/lib/gcc/powerpc-apple-darwin8.3.0/4.0.2/../../
../..`echo /opt/gdc | sed -e 's|^/opt/gdc||' -e
's|/[^/]*|/..|g'`/include/d/4.0.2\" -DD_NO_TRAMPOLINES=1
-DD_CPU_VERSYM=\"PPC\" -DD_OS_VERSYM=\"darwin\"
-DD_PHOBOS_TARGET_DIR=\"/opt/gdc/lib/gcc/powerpc-apple-darwin8.3.0/4.0.2
/../../../..`echo /opt/gdc | sed -e 's|^/opt/gdc||' -e
's|/[^/]*|/..|g'`/include/d/4.0.2/powerpc-apple-darwin8.3.0\"
-DD_GCC_VER=40 -Wno-missing-braces -fmessage-length=0 -DGCC_SAFE_DMD=1
-o d/d-lang.glue.o -c ../../gcc/d/d-lang.cc


../../gcc/toplev.h:67: internal compiler error: Bus error
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://developer.apple.com/bugreporter> for instructions.
gnumake[1]: *** [d/d-lang.glue.o] Error 1
gnumake: *** [all-gcc] Error 2


Date/Time:      2005-11-08 20:26:43.003 +0100
OS Version:     10.4.3 (Build 8F46)
Report Version: 3

Command: cc1plus
Path:    /usr/libexec/gcc/powerpc-apple-darwin8/4.0.0/cc1plus
Parent:  powerpc-apple-darwin8-g++-4.0.0 [918]

Version: ??? (???)

PID:    919
Thread: 0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000048

Thread 0 Crashed:
0   cc1plus 	0x000b1ce4 0x1000 + 724196
1   cc1plus 	0x00098a44 0x1000 + 621124
2   cc1plus 	0x0003f84c 0x1000 + 256076


I'm pretty sure that this has nothing to do with GDC,
so I'll probably have to bugreport with Apple as well...

--anders
November 08, 2005
Anders F Björklund wrote:
> Nope, doing the vanilla build didn't work for me.
> Mac OS X 10.4.3 "Tiger", Xcode 2.1 ("gcc-5026.1")
> 
> Selected outputs from the build: (with GCC 4.0.2)
> 
> 
> c++   -g -O2  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes
> -Wmissing-prototypes     -DHAVE_CONFIG_H -I. -Id -I../../gcc
> -I../../gcc/d -I../../gcc/../include -I./../intl
> -I../../gcc/../libcpp/include     -I. -Id -I../../gcc -I../../gcc/d
> -I../../gcc/../include -I./../intl -I../../gcc/../libcpp/include
> -I../../gcc/d -I../../gcc/d/dmd -Id -D_GNU_SOURCE=1
> -DD_PHOBOS_DIR=\"/opt/gdc/lib/gcc/powerpc-apple-darwin8.3.0/4.0.2/../../
> ../..`echo /opt/gdc | sed -e 's|^/opt/gdc||' -e
> 's|/[^/]*|/..|g'`/include/d/4.0.2\" -DD_NO_TRAMPOLINES=1
> -DD_CPU_VERSYM=\"PPC\" -DD_OS_VERSYM=\"darwin\"
> -DD_PHOBOS_TARGET_DIR=\"/opt/gdc/lib/gcc/powerpc-apple-darwin8.3.0/4.0.2
> /../../../..`echo /opt/gdc | sed -e 's|^/opt/gdc||' -e
> 's|/[^/]*|/..|g'`/include/d/4.0.2/powerpc-apple-darwin8.3.0\"
> -DD_GCC_VER=40 -Wno-missing-braces -fmessage-length=0 -DGCC_SAFE_DMD=1
> -o d/d-lang.glue.o -c ../../gcc/d/d-lang.cc
> 
> 
> ../../gcc/toplev.h:67: internal compiler error: Bus error
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://developer.apple.com/bugreporter> for instructions.
> gnumake[1]: *** [d/d-lang.glue.o] Error 1
> gnumake: *** [all-gcc] Error 2
> 
> 
> Date/Time:      2005-11-08 20:26:43.003 +0100
> OS Version:     10.4.3 (Build 8F46)
> Report Version: 3
> 
> Command: cc1plus
> Path:    /usr/libexec/gcc/powerpc-apple-darwin8/4.0.0/cc1plus
> Parent:  powerpc-apple-darwin8-g++-4.0.0 [918]
> 
> Version: ??? (???)
> 
> PID:    919
> Thread: 0
> 
> Exception:  EXC_BAD_ACCESS (0x0001)
> Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000048
> 
> Thread 0 Crashed:
> 0   cc1plus     0x000b1ce4 0x1000 + 724196
> 1   cc1plus     0x00098a44 0x1000 + 621124
> 2   cc1plus     0x0003f84c 0x1000 + 256076
> 
> 
> I'm pretty sure that this has nothing to do with GDC,
> so I'll probably have to bugreport with Apple as well...
> 
> --anders

This is what I meant by "g++ 4.0.0 is known not to work."  You can build 4.0.0, but you can't use the 4.0.0 g++ to build.

I don't think Apple will fix this.  We'll just have to wait for a new Xcode release.  I work around the problem by using "select_gcc 3.3".

David
November 08, 2005
David Friedman wrote:

> This is what I meant by "g++ 4.0.0 is known not to work."  You can build 4.0.0, but you can't use the 4.0.0 g++ to build.
> 
> I don't think Apple will fix this.  We'll just have to wait for a new Xcode release.  I work around the problem by using "select_gcc 3.3".

Ah, sorry I misunderstood (again) then. Stupid Day today.

I thought you meant *building* with 4.0.0 doesn't work.
Will try with the usual CC=gcc3 CXX=g++3 workaround...

Thanks,
--anders
November 08, 2005
(update)

>> I don't think Apple will fix this.  We'll just have to wait for a new Xcode release.  I work around the problem by using "select_gcc 3.3".
> 
> I thought you meant *building* with 4.0.0 doesn't work.
> Will try with the usual CC=gcc3 CXX=g++3 workaround...

Right, using "gcc3" and "g++3" didn't work much better either.
It choked halfway through the build, on parsing some .y file.

But using "gcc_select 3.3" worked just fine, thanks for that !
Only sad part is that there is no x86 cross-compiler for 3.3 :-)


And it seems that the framework patch was already in, so all good !
Will make for a new 0.16 release of gdcmac, after some packaging...

Panther build will use GCC 3.3.6, Tiger build will use GCC 4.0.2
(I think, if there are no binary problems with it and Apple's GCC)


To be found in the usual location, http://gdcmac.sourceforge.net/

--anders