Red Hat
docs.redhat.com › en › documentation › red_hat_enterprise_linux › 8 › html › developing_c_and_cpp_applications_in_rhel_8 › additional-toolsets-for-development_developing-applications
Chapter 4. Additional toolsets for development | Developing C and C++ applications in RHEL 8 | Red Hat Enterprise Linux | 8 | Red Hat Documentation
GCC Toolset 13 provides the following tools and versions.
Red Hat
docs.redhat.com › en › documentation › red_hat_developer_toolset › 12 › html-single › user_guide › index
User Guide | Red Hat Developer Toolset | 12 | Red Hat Documentation
Replace package_name with a space-separated list of packages that you want to install. For example, to install the devtoolset-12-gdb-gdbserver and devtoolset-12-gdb-doc packages:
Red Hat
access.redhat.com › documentation › en-us › red_hat_developer_toolset › 12 › html-single › 12.0_release_notes › index
12.0 Release Notes | Red Hat Developer Toolset | 12 | Red Hat Documentation
The devtoolset-version-package_name-debuginfo packages can conflict with the corresponding packages from the base Red Hat Enterprise Linux system or from other versions of Red Hat Developer Toolset. This namely applies to devtoolset-version-gcc-debuginfo, devtoolset-version-ltrace-debuginfo, devtoolset-version-valgrind-debuginfo, and might apply to other debuginfo packages, too.
Red Hat
docs.redhat.com › en-us › documentation › red_hat_developer_toolset › 12 › pdf › user_guide › Red_Hat_Developer_Toolset-12-User_Guide-en-US.pdf pdf
Red Hat Developer Toolset 12 User Guide
devtoolset-12-toolchain · Development and debugging · tools · GCC, make, GDB, binutils, elfutils, dwz, memstomp, strace, ltrace · CHAPTER 1. RED HAT DEVELOPER TOOLSET · 13 · To install any of these meta packages: # yum install package_name · Replace package_name with a space-separated list of meta packages you want to install.
Red Hat
docs.redhat.com › en › documentation › red_hat_developer_toolset › 11
Red Hat Developer Toolset | 11 | Red Hat Documentation
Red Hat Developer Toolset | 11 | Red Hat Documentation
Centos
buildlogs.centos.org › c7-devtoolset-12.x86_64 › devtoolset-12-gcc › 20221101234213 › 12.1.1-3.2.el7.x86_64
Index of /c7-devtoolset-12.x86_64/devtoolset-12-gcc/20221101234213/12.1.1-3.2.el7.x86_64
This server contains a mix of raw/unsigned packages and/or build logs It should be used mainly for testing purposes
Red Hat
docs.redhat.com › en › documentation › red_hat_developer_toolset › 12
Red Hat Developer Toolset | 12 | Red Hat Documentation
Red Hat Developer Toolset | 12 | Red Hat Documentation
Developer Community
developercommunity.visualstudio.com › t › linux-supportguide-for-redhat-devtoolset › 1617987
Linux Support/Guide for RedHat devtoolset
Skip to main content · Microsoft · Visual Studio · Sign in · You need to enable JavaScript to run this app · Sorry this browser is no longer supported · Please use any other modern browser like 'Microsoft Edge'
Centos
buildlogs.centos.org › c6-devtoolset-7.x86_64 › Packages
Index of /c6-devtoolset-7.x86_64/Packages
This server contains a mix of raw/unsigned packages and/or build logs It should be used mainly for testing purposes
Oracle Linux
yum.oracle.com › repo › OracleLinux › OL7 › SoftwareCollections › x86_64 › index.html
Oracle Linux 7 (x86_64) Software Collection 3.0 | Oracle, Software. Hardware. Complete.
Oracle Linux with Oracle enterprise-class support is the best Linux operating system (OS) for your enterprise computing needs.
Red Hat
developers.redhat.com › products › red-hat-developer-toolset › overview
Red Hat Developer Toolset | Red Hat Developer
January 21, 2026 - Latest stable versions of GCC (C, C++, Fortran), Eclipse, GDB, SystemTap, and essential development and performance analysis tools.
Red Hat
docs.redhat.com › en › documentation › red_hat_developer_toolset › 12 › html › user_guide › chap-red_hat_developer_toolset
Chapter 1. Red Hat Developer Toolset | User Guide | Red Hat Developer Toolset | 12 | Red Hat Documentation
In addition, certain packages, such as devtoolset-12-gcc-plugin-devel, depend on packages that are only available in the Optional channel.
Red Hat
access.redhat.com › documentation › en-us › red_hat_developer_toolset › 10 › html › user_guide › chap-red_hat_developer_toolset
Chapter 1. Red Hat Developer Toolset | User Guide | Red Hat Developer Toolset | 10 | Red Hat Documentation
Replace package_name with a space-separated list of packages that you want to install. For example, to install the devtoolset-10-gdb-gdbserver and devtoolset-10-gdb-doc packages:
Red Hat
catalog.redhat.com › en › software › containers › rhscl › devtoolset-12-perftools-rhel7 › 62da88bd56b1e977e1ffbb54
Developer Toolset 12 Performance Tools - Red Hat Ecosystem Catalog
June 5, 2024 - rhscl/devtoolset-12-perftools-rhel7 ... authentication. View · other options. On June 30th, 2024, Red Hat Enterprise Linux 7 will transition from Maintenance Life Cycle 2 phase to Extended Life phase....
Top answer 1 of 5
93
In your ~/.bashrc or ~/.bash_profile Simply source the "enable" script provided with the devtoolset. For example, with the Devtoolset 2, the command is:
source /opt/rh/devtoolset-2/enable
or
source scl_source enable devtoolset-2
Lot more efficient: no forkbomb, no tricky shell
2 of 5
17
An alternative of source /opt/rh/devtoolset-4/enable is
source scl_source enable devtoolset-4
The above shell script scl_source is more elegant than using a hard coded path (may be different on another machine). However scl_source does less because /opt/rh/devtoolset-4/enable uses scl_source and other stuff.
To use scl_source you may have to upgrade package scl-utils
yum update scl-utils # old scl-utils versions miss scl_source
Quick copy-paste
echo 'source scl_source enable devtoolset-4' >> ~/.bashrc
# Do not forget to change the version ↑
Source code for curious people
An example of scl_source source code:
https://gist.github.com/bkabrda/6435016
The scl_source installed on my Red Hat 7.1
#!/bin/bash
_scl_source_help="Usage: source scl_source <action> [<collection> ...]
Don't use this script outside of SCL scriptlets!
Options:
-h, --help display this help and exit"
if [ $# -eq 0 -o $1 = "-h" -o $1 = "--help" ]; then
echo "$_scl_source_help"
return 0
fi
if [ -z "$_recursion" ]; then
_recursion="false"
fi
if [ -z "$_scl_scriptlet_name" ]; then
# The only allowed action in the case of recursion is the same
# as was the original
_scl_scriptlet_name=$1
fi
shift 1
if [ -z "$_scl_dir" ]; then
# No need to re-define the directory twice
_scl_dir=/etc/scl/conf
if [ ! -e $_scl_dir ]; then
_scl_dir=/etc/scl/prefixes
fi
fi
for arg in "$@"; do
_scl_prefix_file=$_scl_dir/$arg
_scl_prefix=`cat $_scl_prefix_file 2> /dev/null`
if [ $? -ne 0 ]; then
echo "Can't read $_scl_prefix_file, $arg is probably not installed."
return 1
fi
# First check if the collection is already in the list
# of collections to be enabled
for scl in ${_scls[@]}; do
if [ $arg == $scl ]; then
continue 2
fi
done
# Now check if the collection isn't already enabled
/usr/bin/scl_enabled $arg > /dev/null 2> /dev/null
if [ $? -ne 0 ]; then
_scls+=($arg)
_scl_prefixes+=($_scl_prefix)
fi;
done
if [ $_recursion == "false" ]; then
_i=0
_recursion="true"
while [ $_i -lt ${#_scls[@]} ]; do
_scl_scriptlet_path="${_scl_prefixes[$_i]}/${_scls[$_i]}/${_scl_scriptlet_name}"
source "$_scl_scriptlet_path"
if [ $? -ne 0 ]; then
echo "Can't source $_scl_scriptlet_name, skipping."
else
export X_SCLS="${_scls[$_i]} $X_SCLS"
fi;
_i=$(($_i+1))
done
_scls=()
_scl_prefixes=()
_scl_scriptlet_name=""
_recursion="false"
fi