------- Comment #1 from mikpe at it dot uu dot se 2009-09-30 01:27 ------- I just rebuilt a vanilla gcc-4.4.1 with itself on armv5tel-linux-gnueabi, and as usual there were no problems. I even used your LDFLAGS=-Wl,-O1 and STAGE1_CFLAGS=-O settings.
A few notes: - you seem to be building in the source dir; I don't think that's supported, I haven't done that in a decade or so - in the gentoo bug entry there is an indication that you're using binutils-2.18, I'm using binutils-2.19.1; normally I wouldn't worry but you're passing -O1 to ld so who knows? - in the gentoo bug entry there is some speculation that gcc runs out of memory on 512MB RAM machines; I've rebuilt 4.4.1 with itself on arm boxes with as little as 64MB without much problems (as long as java is disabled); of course you need ample swap, at least temporarily - I don't think "-pipe" is a good idea on small memory machines - I do use --enable-checking=release to avoid gcc growing too large and slow, that may be a factor given the size-related post-4.3 bootstrap failure PR I'm not convinced this is a gcc-4.4.1 bug. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41500
