GCC 3.3 compilation on PowerPC / Darwin
nick at dsvr.net
Wed Jul 23 01:07:14 PDT 2003
John Tytgat wrote:
> In message <3F1D0082.20903 at dsvr.net>
> Nick Burrett <nick at dsvr.net> wrote:
>>You take a PowerPC machine running Darwin, configure GCC 3.3 on that,
>>then inspect the resultant config.h, hconfig.h and tconfig.h header
>>files. That will then tell you which headers you need to import.
> After re-reading Q4 I understand what's mentioned there. But GCC 3.3
> has moved on since the snapshot has been taken. Doesn't it make sense
> to update as well (now that it is nearly frozen) so that we can have the
> latest bugfixes as well ?
Erm. Yes, it does. I am thinking of importing the GCC 3.4 branch
The libstdc++ guys reckon that the library should work without wide
character support. So armed with that news, I'll have another crack at
>>>>gcc -g -O2 -DTARGET_RISCOSAOF -DCROSS_COMPILE -DHOST__ -DIN_GCC -DHAVE_CONFIG_H -o /Users/joty/Develop/gccsdk/arm-riscos-aof/gcc-3_3_0/gcc/stage1/c-convert.o -c c-convert.c -I./ -I../../include -I./config
>>Note that 'host_system' in configure.in hasn't been correctly set. Did
>>you run autoconf ?
> Yes I did, but probably I fooled myself when rerunning things, that not
> everything gets automatically regenerated. I restarted from scratch and
> now have a proper HOST_POWERPC_DARWIN defined.
It's a half-arsed build system that was originally designed to allow the
GCCSDK to be compiled on both RISC OS and Unix. I had just stuck to
Unix, then we would have a fully autoconf enabled build system, with
dependencies and all such wonderful things. One for the ToDo list :-)
>>>>gcc -g -O2 -DTARGET_RISCOSAOF -DCROSS_COMPILE -DHOST__ -DIN_GCC -DHAVE_CONFIG_H -o /Users/joty/Develop/gccsdk/arm-riscos-aof/gcc-3_3_0/gcc/stage1/c-aux-info.o -c c-aux-info.c -I./ -I../../include -I./config
>>>>gcc -g -O2 -DTARGET_RISCOSAOF -DCROSS_COMPILE -DHOST__ -DIN_GCC -DHAVE_CONFIG_H -o /Users/joty/Develop/gccsdk/arm-riscos-aof/gcc-3_3_0/gcc/stage1/c-common.o -c c-common.c -I./ -I../../include -I./config
>>>>builtin-attrs.def:115: missing right curly brace, found `_0'
>>>>builtin-attrs.def:115: illegal external declaration, missing `;' after `ATTR_FORMAT_PRINTF_1'
>>It's better to get the configure stuff working properly before you start
>>to tackle errors like this.
> Still get this one, but maybe because of the above mentioned config.h, etc
> files ?
I think that is highly likely.
Network Engineer, Designer Servers Ltd. http://www.dsvr.co.uk
More information about the gcc