Talk:Upgrading GCC

Hrm. I don't think using "FUD" to describe the previous version of this page is very chummy. I'm going to change it. Also, the references to "rebuilding everything" on the old page were for *complete assurance* of compatibility, not FUD or otherwise due to a lack of understanding. Can this page now guarantee this for those who follow the present version? --NightMonkey (talk) 22:35, 28 January 2015 (UTC) Sure, why don't you.--jer (talk) 11:59, 29 January 2015 (UTC)

Do we need to escape the periods?
The code currently suggests to escape the periods, like so:

The command works just fine without this. Wouldn't it be much user friendlier to keep it as such then?

--SwifT (talk) 18:33, 11 August 2015 (UTC)


 * --library can be a regular expression, so I escaped dot to avoid ambiguity, but yes, the version without escape characters is equivalent to the escaped version. I'm going to remove the dot to cure the Leaning Toothpick Syndrome in the code. Biergaizi (talk)

--Ormaaj (talk) 11:01, 12 August 2015 (UTC) GCC 6.1 released.
 * I left in the dot escapes because the manual says it interprets the argument as a BRE unless it's a full path to a library. Ideally there would be a better way to obtain the soname from the current gcc configuration using scanelf perhaps.