On 28/05/13 01:28, William Harrington wrote:
Greetings fellow CLFS builders,

We are needing to update gcc.

I'm fond of updating gcc to 4.7.3 rather than 4.8.0. I mentioned earlier that graphite had issues with 4.8.0 with throwing segfaults everywhere. I went to 4.7.3 an didn't have issues. The author of 0linux has the same thought, and sticks with 4.7.3 as of now. I know gcc 4.8.0 has a lot of features which people will want, and 4.7.3 isn't far behind, but it is more stable as of now, as far as I'm concerned with graphite. CLFS includes graphite, and so it seems important that graphite work properly. I do not know what gcc 4.8.0 has which causes graphite to be a problem. 4.7.x is fine. It could be a problem with cloog-isl or some other graphite component.

Should we go for GCC 4.7.x or 4.8.0? I'm shooting for 4.7.x.

What we want is stability. The last thing we want is someone building CLFS with gcc 4.8.0 then wanting to use graphite options and then everything segfaults all over the place. Or we could use gcc 4.7.3 and graphite options don't cause segfaults all over the place.
4.8.0,. allows us to remove ppl which takes a long time to check, we have always been cautious with optimisation in builds as they often cause problems whatever they are.

Have encountered no major problems with 4.8.0 and 4.8.1 will be out in a week or so

Common problems with gcc 4.8.0 and graphite: ncurses and readline. Those caused the most issues with my experimental builds.

Sincerely,

William Harrington
_______________________________________________
Clfs-dev mailing list
Clfs-dev@lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org

martin

_______________________________________________
Clfs-dev mailing list
Clfs-dev@lists.cross-lfs.org
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org

Reply via email to