$summary
Created attachment 276405 [details] re-patched gcc-patches for 4.5.3 removed a few patches for 4.5.2 that seem to be already applied upstream...
with this patch, ebuild for gcc-4.5.2 works for 4.5.3 too. copy the gcc-4.5.2.ebuild in your private tree as gcc-4.5.3.ebuild, copy the attachment into distfiles, copy existing gcc-4.5.2-piepatches-v0.4.5.tar.bz2 to gcc-4.5.3-piepatches-v0.4.5.tar.bz2 and gcc-4.5.2-uclibc-patches-1.0.tar.bz2 to gcc-4.5.3-uclibc-patches-1.0.tar.bz2 You should have them in distfiles map if you have emerged gcc-4.5.2. If not, you will have to fetch the files first ( emerge -F =gcc-4.5.2) after that you can make manifest for new ebuild and emerge new gcc It works for me. So far, without any troubles...
Any progress with this?
No.
(In reply to comment #4) > No. Why not?
Built just fine for me.
(In reply to comment #5) > (In reply to comment #4) > > No. > > Why not? Because there aren't enough hours in a day. It's on my list, but my list is kinda huge at the moment.
Heh, the way you just said "no" worried me that there's some kind of technical problem here. Glad to hear that's not the case.
Let us know if there is anything we can provide that could be of use for you. Meanwhile, here's the list of fixes: http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.5.3 Maybe something from our tracker has been fixed? https://bugs.gentoo.org/show_bug.cgi?id=gcc-4.5
We're a few days more than 3 months after the release of 4.5.3. I understand that you're busy, so would you mind if someone else (maybe not on toolchain@) did this bug? Are there any special things that need to be done for gcc bumps?
(In reply to comment #10) > We're a few days more than 3 months after the release of 4.5.3. I understand > that you're busy, so would you mind if someone else (maybe not on toolchain@) > did this bug? > > Are there any special things that need to be done for gcc bumps? I'll have it done this week.
Bumped, sorry about the wait.