Tim, Darrel, All,
Hell Yes! The nasty kwrite crash on line-wrap when built with gcc 4.7.0-x is _fixed_ when built with gcc 4.7.1! Damn I hate gcc transitions! To think about the time lost because somebody botched the latest and greatest update to the underpinnings for all software just boggles the mind. Not just on TDE, but globally, just think about the man-hours lost chasing bugs that ended up being due to a gcc bug.... Wow! Same thing happened with the update to 4.5.2 during the spring of 2011. Lesson - don't put out new versions of anything during the spring when gcc is likely to throw you a curve ball...
Regardless, kwrite is _working fine_! That gets a second *Hell Yes!*
On 06/20/2012 11:15 AM, David C. Rankin wrote:
Tim, Darrel, All,
Hell Yes! The nasty kwrite crash on line-wrap when built with gcc 4.7.0-x is _fixed_ when built with gcc 4.7.1! Damn I hate gcc transitions! To think about the time lost because somebody botched the latest and greatest update to the underpinnings for all software just boggles the mind. Not just on TDE, but globally, just think about the man-hours lost chasing bugs that ended up being due to a gcc bug.... Wow! Same thing happened with the update to 4.5.2 during the spring of 2011. Lesson - don't put out new versions of anything during the spring when gcc is likely to throw you a curve ball...
Regardless, kwrite is _working fine_! That gets a second *Hell Yes!*
Bug 979 closed NOTOUTPROBLEM. Screenshot:
http://nirvana.3111skyline.com/dl/dt/trinity/ss/kwrite-gcc_4.7.1-fixed.jpg
:)
On 06/20/2012 11:15 AM, David C. Rankin wrote:
Tim, Darrel, All,
Hell Yes! The nasty kwrite crash on line-wrap when built with gcc 4.7.0-x is _fixed_ when built with gcc 4.7.1! Damn I hate gcc transitions! To think about the time lost because somebody botched the latest and greatest update to the underpinnings for all software just boggles the mind. Not just on TDE, but globally, just think about the man-hours lost chasing bugs that ended up being due to a gcc bug.... Wow! Same thing happened with the update to 4.5.2 during the spring of 2011. Lesson - don't put out new versions of anything during the spring when gcc is likely to throw you a curve ball...
Regardless, kwrite is _working fine_! That gets a second *Hell Yes!*
Confirmed fixed on both i686 & x86_64 on Arch.
On Jun 26, 2012, at 11:25, "David C. Rankin" drankinatty@suddenlinkmail.com wrote:
On 06/20/2012 11:15 AM, David C. Rankin wrote:
Tim, Darrel, All,
Hell Yes! The nasty kwrite crash on line-wrap when built with gcc 4.7.0-x is _fixed_ when built with gcc 4.7.1! Damn I hate gcc transitions! To think about the time lost because somebody botched the latest and greatest update to the underpinnings for all software just boggles the mind. Not just on TDE, but globally, just think about the man-hours lost chasing bugs that ended up being due to a gcc bug.... Wow! Same thing happened with the update to 4.5.2 during the spring of 2011. Lesson - don't put out new versions of anything during the spring when gcc is likely to throw you a curve ball...
Regardless, kwrite is _working fine_! That gets a second *Hell Yes!*
Confirmed fixed on both i686 & x86_64 on Arch.
-- David C. Rankin, J.D.,P.E.
gcc 4.7.1 fixed a LOT of problems that were encountered with 4.7.0. Make sure that everything still works if you applied a patch for 4.7.0 :)
-- later, Robert Xu
On 06/26/2012 11:24 AM, Robert Xu wrote:
Confirmed fixed on both i686 & x86_64 on Arch.
-- David C. Rankin, J.D.,P.E.
gcc 4.7.1 fixed a LOT of problems that were encountered with 4.7.0. Make sure that everything still works if you applied a patch for 4.7.0 :)
-- later, Robert Xu
Tim, Darrell,
This brings up a BIG issue. Might we need to revert some of the gcc 4.7.0 patches? The it -> it2 stuff shouldn't matter, but then again... I can't explain the krusader build failure.
On 26 Jun 2012, David C. Rankin stated:
This brings up a BIG issue. Might we need to revert some of the gcc 4.7.0 patches? The it -> it2 stuff shouldn't matter
That was required due to an intentional change in GCC 4.7 for better conformance to the C++ Standard, so it's not likely to be reverted in point releases (or at all). (If it *did* somehow get reverted, *that* would be a bug in GCC.)
This brings up a BIG issue. Might we need to revert some of the gcc 4.7.0 patches? The it -> it2 stuff shouldn't matter, but then again... I can't explain the krusader build failure.
The only gcc 4.7 patch for krusader I see was commit fdf6d340, which was explicitly declaring "using namespace std;" in krusader/UserAction/tstring.h.
Darrell
-
Darrell Anderson -
David C. Rankin -
Nix -
Robert Xu