Message: previous - next
Month: April 2012

Re: [trinity-devel] gcc 4.7 support

From: Darrell Anderson <humanreadable@...>
Date: Fri, 27 Apr 2012 23:04:50 -0700 (PDT)
> If you update or improve patches, please post updates
> to 958. Unless you have somewhere else you would rather collect them all, I say we
> just work all gcc47 patches in bug 958 since that is where the collection of
> patches currently resides. I have made a point to upload all of the gcc47
> patches I have there.

Check the commit web page tomorrow and you'll find quite a few patches pushed. :-)

I spent the past two days testing the various gcc 4.7 patches and updating for GIT. I am almost finished with an almost complete build set. Meaning there is almost nothing left to patch. You and Francois did most of the patching.

I patched a few more apps and have not yet pushed to GIT. I followed the GCC 4.7 Porting guide and the patches the two of you created.

Therefore I am thinking of closing bug report 958 Real Soon Now. Thereafter we can open package-specific bug reports as needed. Bug report 958 is getting cumbersome to filter through and has served its purpose. All of the patches but one have been pushed.

The only remaining patch from 958 is for koffice, which I had to split into two. The libpng portion needed preprocessor checks to apply the changes only for libpng 1.5. Although Slackware Current is now using gcc 4.7, libpng 1.4.9 is still used and the original patch failed on my system. So I added the same checks we used for gwenview and digikam. I still need to test that split but I think the gcc 4.7 headaches are behind us.

> Also, after you gcc47 builds of tdelibs and tdebase,
> test the kwrite/kate lockup issue that is presently 979. That will help rule in
> or rule out gcc47 as an issue.

Okay. I'll try to remember. I should disappear for a few days. :-) Tim and I beat up our heads all week resolving TSAK/TDM and desktop locking issues. He hacked and I did my usual breakage testing. Both TSAK/TDM and locking are now in good shape. Anybody waiting on those fixes should try a clean build from GIT to test whether their related pet peeves are resolved.