How to test toolchain components (gcc, glibc, binutils)

Seems obviously for many of you, but a lot of people in the past, have asked me how to test toolchain components and be sure to don’t break anything.

Ok, as usual we will start to test the singular package with multiple USE combinations. Don’t expect that should work with USE=”vanilla”; for who don’t know:

Do not add extra patches which change default behaviour; DO NOT USE THIS ON A GLOBAL SCALE as the severity of the meaning changes drastically

If the various tests passes without build failure, now, you should try to recompile your system, to check if the new package could break something, so:
emerge -e system

If there are failures, check if them are related to what you are testing(e.g. don’t post zlib failures when you test binutils). If you don’t know how to understand who causes the failure, just poke a developer on irc.

If you have a powerful machine, instead of re-emerge system please do:
emerge -e world

Obviously for failures, file a bug and block the stabilization bug or the tracker.

This entry was posted in arch testing, gentoo. Bookmark the permalink.

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.