On 06/27/2012 11:30 PM, Timothy Pearson wrote: >> All, >> >> Also noted from the meeting, the current 3.5.13 will _not_ build on gcc >> 4.7.1. >> There is _no_ reason not to port the patches to the 3.5.13 code base. All >> the >> patches simply cleaned up the code from a syntax standpoint and will not >> impact >> it building on earlier gcc releases. The closed bug 979 holds the >> collection of >> gcc 4.7 patches that could easily be applied to 3.5.13 to make it gcc >> 4.7.1 >> compliant. > > Have those applications that were affected by the gcc patches been fully > and completely tested? If not we would risk introducing regressions into > an SRU. > > Tim > I have beat up on them fairly well -- all the way down to correcting konsole 'tips of the day'.. Darrell has been testing heavily as well. I do think your caution is well founded though and I would like to see the development get to the point where 14 is considered "ready for a major code change freeze" so we can get binaries out to more people for testing. I don't think they will uncover much, but I would like the confirmation from multiple distros and multiple users. How many is enough?? 50? 100 installs? Worth considering and setting a target... -- David C. Rankin, J.D.,P.E.