On Fri, May 18, 2012 at 10:53 PM, Jay K <jay.kr...@cornell.edu> wrote:
>
> /src/gcc-4.7.0/configure -disable-bootstrap -enable-languages=go
>
>
> book2:gccgo-4.7 jay$ g++ -v
> Using built-in specs.
> Target: i686-apple-darwin9
> Configured with: /var/tmp/gcc/gcc-5493~1/src/configure --disable-checking 
> -enable-werror --prefix=/usr --mandir=/share/man 
> --enable-languages=c,objc,c++,obj-c++ 
> --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ 
> --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib 
> --build=i686-apple-darwin9 --with-arch=apple --with-tune=generic 
> --host=i686-apple-darwin9 --target=i686-apple-darwin9
> Thread model: posix
> gcc version 4.0.1 (Apple Inc. build 5493)
>
>
> a lot of:
>
> /usr/include/c++/4.0.0/tr1/functional_iterate.h:912: error: cannot use typeid 
> with -fno-rtti
> /src/gcc-4.7.0/gcc/go/gofrontend/string-dump.h: At global scope:

This is using TR1.  So the question is whether the Go front-end is using
it just as a convenience whether it really needs TR1 and the implied
RTTI (typeid).

-- Gaby

Reply via email to