Hello, please consider to add these two hints to gcc upgrade guide: 1. -march instead of -mcpu CFLAG should be used (some packages will otherwise break the emerging process). for further reading there could be link http://gentoo-wiki.com/CFLAGS. 2. emerge --resume --skipfirst could be used when emerge fails and you need to continue rebuilding system even without that package. Reproducible: Always Steps to Reproduce:
We don't discuss CFLAGS or CXXFLAGS in the gcc upgrade guide because it's not necessary to do so. Read the various arch handbooks to see suggested CFLAGS for each arch. Also, we don't link to gentoo-wiki. Finally, though --resume --skipfirst is nice from a user's point of view (when emerging system overnight), it's still not good for a healthy system, as it just postpones dealing with an error, rather than fixing it. It's not really a solution.
ad 1. i didn't want to make discussion about cflags, but just the notion, that getting newer gcc you should reconsider the setting, you have done years back. ad 2. i see your point. in my case i resumed & skipped the last package and in next console just fixed it (i.e. unmerged it from the whole system, because the problem was not in compilation, but in undownloadable sources). if you know better way how to do it, please tell me. (remerging the world again is a nightmare, when it happens more time - and it happened ...).
