How to Install and Uninstall gcc-toolset-12-binutils-devel.x86_64 Package on Red Hat Enterprise Linux 9 (RHEL 9)

Last updated: October 14,2024

1. Install "gcc-toolset-12-binutils-devel.x86_64" package

This guide let you learn how to install gcc-toolset-12-binutils-devel.x86_64 on Red Hat Enterprise Linux 9 (RHEL 9)


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                gcc-toolset-12-binutils-devel.x86_64
            
                    
    
    Copied

2. Uninstall "gcc-toolset-12-binutils-devel.x86_64" package

This guide covers the steps necessary to uninstall gcc-toolset-12-binutils-devel.x86_64 on Red Hat Enterprise Linux 9 (RHEL 9):


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                gcc-toolset-12-binutils-devel.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the gcc-toolset-12-binutils-devel.x86_64 package on Red Hat Enterprise Linux 9 (RHEL 9)

Last metadata expiration check: 1:02:11 ago on Mon Feb 26 07:04:30 2024.
Available Packages
Name : gcc-toolset-12-binutils-devel
Version : 2.38
Release : 19.el9
Architecture : x86_64
Size : 12 M
Source : gcc-toolset-12-binutils-2.38-19.el9.src.rpm
Repository : ubi-9-appstream-rpms
Summary : BFD and opcodes static and dynamic libraries and header files
URL : https://sourceware.org/binutils
License : GPLv3+
Description : This package contains BFD and opcodes static and dynamic libraries.
:
: The dynamic libraries are in this package, rather than a separate
: base package because they are actually linker scripts that force
: the use of the static libraries. This is because the API of the
: BFD library is too unstable to be used dynamically.
:
: The static libraries are here because they are now needed by the
: dynamic libraries.
:
: Developers starting new projects are strongly encouraged to consider
: using libelf instead of BFD.