gcc 4.8.0+ has trouble compiling GCC 4.6.3

[kallisti5]

gcc 4.8.0+ has trouble compiling GCC 4.6.3.

[vsyscall]
/home/kallisti5/Projects/buildtools/gcc/libgcc/../gcc/libgcc2.c: In function
'__negdi2':
/home/kallisti5/Projects/buildtools/gcc/libgcc/../gcc/libgcc2.c:72:1: internal
compiler error: Aborted
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [_negdi2.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory
`/home/kallisti5/Projects/haiku/generated/cross-tools-build/gcc/i586-pc-haiku/libgcc'
make[1]: *** [all-target-libgcc] Error 2
make[1]: Leaving directory

GCC bug: ​http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56938

[kallisti5]

almost forgot to note the solution.

It's recommended to update to GCC 4.6.4 as it contains a fix for this issue. It is unlikely anyone is going to see this unless they are crazy like me and run ArchLinux :)

[jprostko]

Replying to kallisti5:

almost forgot to note the solution.

It's recommended to update to GCC 4.6.4 as it contains a fix for this issue. It is unlikely anyone is going to see this unless they are crazy like me and run ArchLinux :)

I am running Manjaro on a partition, so I can relate. :) That said, I haven't tried a Haiku build on it yet in order to notice. I can probably push GCC 4.6.4 sometime this week, although admit I'd like to try getting 4.7.3 or 4.8.0 building yet for Haiku. Getting 4.7.2 building for Haiku isn't totally trivial (for the cross-build anyway), but I'm hoping the GCC guys fixed some broken dependency things in the meantime in 4.7.3 and/or 4.8.0 that will make things easier to deal with.

I'll mark the ticket as in-progress once I get my dev environment set up. I think I'll just re-install Linux Mint on another partition so I can at least get Haiku built with it. I doubt they use anything close to GCC 4.8.0. :)

[korli]

Just noticed this ticket.. 4.6.4 is merged since btrev43055. Can this be closed as fixed?

[jprostko]

Korli, thank you for the commit! I suppose this could be closed as fixed (since it does fix the issue), but shouldn't we add native GCC 4.6.4 optional packages for x86 and x86_64 just to be "complete"? I tried doing as much earlier today, but it seems this laptop likes to conveniently overheat and shutdown on me. If it wasn't obvious, I need better dev machines handy! :)

Then again, as I mentioned previously, maybe we should just wait for GCC 4.7 or 4.8 to build out new packages.

[korli]

Replying to jprostko:

Korli, thank you for the commit! I suppose this could be closed as fixed (since it does fix the issue), but shouldn't we add native GCC 4.6.4 optional packages for x86 and x86_64 just to be "complete"? I tried doing as much earlier today, but it seems this

I was expecting maybe the current package management effort would include this adding an optional package for GCC4, as it did for GCC2 :)

Alexander, I'm marking as fixed. Please reopen if needed.