From 3db6371539e89ade2c992ee33297716d629ab35e Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Wed, 23 Jan 2019 10:35:50 +0100 Subject: user: Use capital letters for acronyms Fix GCC definition. --- user/rsb/why-build-from-source.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'user/rsb/why-build-from-source.rst') diff --git a/user/rsb/why-build-from-source.rst b/user/rsb/why-build-from-source.rst index 5d88e0c..eefeade 100644 --- a/user/rsb/why-build-from-source.rst +++ b/user/rsb/why-build-from-source.rst @@ -33,8 +33,9 @@ an equivalent tool set. Building from source provides you with control over the configuration of the package you are building. If all or the most important dependent parts are built from source you limit the exposure to host variations. For example the -GNU C compiler (gcc) currently uses a number of third-party libraries internally -(gmp, mpfr, etc). If your validated compiler generating code for your target +GNU Compiler Collection (GCC) currently uses a number of third-party libraries +internally (GMP, ISL, MPC, MPFR, etc.). If your validated compiler generating +code for your target processor is dynamically linked against the host's version of these libraries any change in the host's configuration may effect you. The changes the host's package management system makes may be perfectly reasonable in relation to the -- cgit v1.2.3