summaryrefslogtreecommitdiffstats
path: root/development/gcc5/README
diff options
context:
space:
mode:
author B. Watson2022-02-28 19:17:58 +0100
committer Willy Sudiarto Raharjo2022-03-01 13:35:41 +0100
commit151eceb5062af1a1f8231467938aa0388e23ee51 (patch)
tree155555b59f2c8ce12e2b858833e9ad940cae5a36 /development/gcc5/README
parent69e67750d40c506933fb5e3da66576ccba8307d2 (diff)
downloadslackbuilds-151eceb5062af1a1f8231467938aa0388e23ee51.tar.gz
development/gcc5: Speed up find/chmod.
Signed-off-by: B. Watson <yalhcru@gmail.com> Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'development/gcc5/README')
-rw-r--r--development/gcc5/README36
1 files changed, 19 insertions, 17 deletions
diff --git a/development/gcc5/README b/development/gcc5/README
index 043d62efcf..bdc9fd7e52 100644
--- a/development/gcc5/README
+++ b/development/gcc5/README
@@ -1,24 +1,25 @@
-This gcc5 package can be installed alongside Slackware's gcc-7 packages.
-These version 7 compilers can sometimes be quite a bit more strict about
-what they accept as valid code. As a consequence, you will regularly run
-into compilation issues with software. Not just the software made with
-the scripts on slackbuilds.org, but also some of the software in
-the Slackware core distribution requires patches in order to get them
-to compile.
+This gcc5 package can be installed alongside Slackware's gcc-11
+packages. These version 11 compilers can sometimes be quite a bit
+more strict about what they accept as valid code. As a consequence,
+you will regularly run into compilation issues with software. Not just
+the software made with the scripts on slackbuilds.org, but also some
+of the software in the Slackware core distribution requires patches in
+order to get them to compile.
Still having the gcc version 5 compilers can sometimes be a lifesaver.
Particulars of the gcc5 package:
- The gcc5 binaries were given a suffix '-5' to make them stand apart
from Slackware's default compilers.
-- The gcc5 package only contains the C, C++ and Java language compilers.
+- The gcc5 package only contains the C, C++ and Java compilers.
- One all-encompassing package is built by the SlackBuild script.
- Profile scripts are added to /etc/profile.d/. You can 'source'
the profile script to prefer the gcc-5 compilers over gcc-7.
- On 64bit Slackware, the gcc5.SlackBuild will detect an existing gcc
multilib compiler and will then build a multilib capable gcc5.
- If you run pure 64bit Slackware, then a pure 64bit gcc5 package is built.
+ If you run pure 64bit Slackware, then a pure 64bit gcc5 package is
+ built.
-How to use these gcc5 compilers instead of Slackware's default C and C++?
+How to use these gcc5 compilers instead of Slackware's default ones?
Simple:
In your console or terminal, you 'source' the provided profile script,
like this (a c-shell compatible script is available as well):
@@ -26,8 +27,9 @@ like this (a c-shell compatible script is available as well):
source /etc/profile.d/gcc5.sh
The command 'source' is equivalent to the dot command ' . '.
-The profile script will (re-)define the common variables that are used
-by make and other programs to determine which binary to run as the compiler:
+The profile script will (re-)define the common variables that are
+used by make and other programs to determine which binary to run as
+the compiler:
export CC=gcc-5
export CPP=cpp-5
@@ -38,9 +40,9 @@ export RANLIB=gcc-ranlib-5
Nothing else needs to be done after sourcing the profile script.
All you do next is run your compile job as usual in that same console.
-Your program will be compiled with the binaries provided by the gcc5 package.
-
-** WARNING:
-** The temporary build location used by the script (defaulting here to /tmp/SBo)
-** should *NOT* be a directory path a non-root user could create later...
+Your program will be compiled with the binaries provided by the gcc5
+package.
+** WARNING: The temporary build location used by the script
+** (defaulting here to /tmp/SBo) should *NOT* be a directory path a
+** non-root user could create later...