Created attachment 345316 [details] whole patches tarbzip... I have tweaked ebuild and patches for existing gcc-4.7.2-r1 to accomodate fresh gcc-4.7.3. Since I am not gcc maintainer and do not have deep insight into gcc's inner workings, I might fucked up something. I did: 1. copied gcc-4.7.2-r1 ebuild into my repository as gcc-4.7.3.ebuild 2. within distfiles directory a.copied existing gcc-4.7.2-piepatches-v0.5.5.tar.bz2 as gcc-4.7.2-piepatches...tar.bz2 ( I changed only "2" to "3" in the name ) b. ditto with gcc-4.7.2-uclibc-patches-1.0.tar.bz2 3. a. untarbzipped gcc-4.7.2-patches-1.5.tar.bz2 into /usr/src/patch b. deleted: 82_all_alpha_4.6.4_pr56023_bootstrap.patch 93_all_pr33763_4.7.3_extern-inline.patch 94_all_pr53708_4.7.3_user-alignment.patch 95_all_pr55940_4.7.3_x86-stack-parameters.patch 96_all_pr56125_4.7.3_ffast-math-pow.patch c. made minor change to 90_all_gcc-4.7-x32.patch ( basically deleted one of the last diffs, pertaining to libstdc++-v3/configure as this was already applied) 4. tarbzipped remaining files in the patch map back to gcc-4.7.3-patches-1.5.tar.bz2 and copied it to distfiles map 5. made ebuild my_new_gcc-4.7.3.ebuid manifest 6. emerged new gcc I took all patches from existing gcc-4.7.2-r1 ebuild, so if you are starting from different gcc, you might want to unmask it and do an emerge -F =gcc-4.7.2-r1" so that you get starting patches. I have attached whole gcc-4.7.3-patches-1.5.tar.bz2 for reference.
Above recipe is missing to copy also $portdir/sys-devel/gcc/files I have recompiled a lot with this new gcc-4.7.3 (unmasked ffmpeg-1.2 and USE=-aac) And rebooted to see if all went well. Confirming! I didn't expect any other result though :) Many thanks Branko!
Please add the 4.7.3 ebuild to the portage tree soon.
I can confirm running gcc-4.7.3 without issues since ten days. @theodor, can be that Gentoo maintainers had added all the bug fix packages on the way to gcc-4.7.3 already?! And they think this would be a pointless version bump therefore (I can tell you I hadn't had an issue with gcc-4.7.2 either).
It'll get bumped when it's ready. I'm working on it.
(In reply to comment #3) > @theodor, > can be that Gentoo maintainers had added all the bug fix packages on the way > to gcc-4.7.3 already?! Please refrain from speculative rhetorical questions and inform yourself instead. @Ryan Thank you for taking care of it!
(In reply to comment #4) > It'll get bumped when it's ready. I'm working on it. Out of curiosity, what does it need to get ready? I expect that adding it (as unstable) to the tree will show any problems quicker than holding it back without doing much damage or am I mistaken?
I have a bunch of eclass changes I need to make, plus go through all the open 4.7 bugs. It'll be done by this weekend for sure.
In the meantime for those like me who would like to try this new version out. I've written this ebuild that I began using last week. Basically it does what the OP did without the pain of extracting the unneeded patches from the latest 4.7.2 1.6-patch tarball. Instead it just excludes installing the unneeded patches. Because of this I don't advise anyone using x32 to try since it doesn't modify the 90_all_gcc-4.7-x32.patch. All one needs to do is put this ebuild in their overlay and install. So far it works like a charm. Enjoy Ciao
Created attachment 348094 [details] gcc-4.7.3.ebuild Updated ebuild for sys-devel/gcc-4.7.3.ebuild
Created attachment 348098 [details] gcc-4.7.3.ebuild I uploaded the previous ebuild with the wrong mime-type so it was unreadable in my browser.
Good to have working ebuild(s) lying around. Altough, as ryao said, I'd recommend waiting a little longer until it's certain there won't be any problems for anyone after bumping 4.7.3 into portage.
Had a last minute fix to make. Bumped.
So, where is it ? It's not in main tree yet. Should we look in some overlay ?
It's in the tree. Try again.
True. I emerged it. I couldn't see it in the first place because I had gcc-4.7.3.ebuild in my overlay and until I renamed it to some¸thing else, "equery list -i -p gcc" wouldn't show it, even though it was there. Thanks...
