------- Comment #15 from WISD00M at GMX dot NET 2006-09-13 00:36 ------- > No it does not. Well, as I said: it's just an assumption-for the lack of a better explanation right now.
>Are you sure you don't have some bad hardware? well, define "bad hardware"-the system works without any problems whatsoever, no crashes, no performance issues, no nothing. In fact, it does compile other software without any problems, too-it even compiled gcc 4.01. So, I have really no reason to believe that this is due to some sort of hardware issue. Neither do I believe this to be some sort of gcc-internal bug. Rather, I have come to believe that somewhere along the build process (for whatever reason), gcc 4.2 is made believe that it should assume 64bit as default target platform. Otherwise, I'm really not sure why it would create an cc1 executable that terminates immediatley with the aforementioned error, when it's started without the "-m32" flag. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29049
