Red hat enterprise linux install gcc

Check the system version:

yum in red hat requires payment

There are two main ways to solve this problem:

1. Install through yum, the first one is through yum replaced with CentOS, and then installed directly with yum install gcc;

The second method is to install through a local mirror file, and use iso as a yum library (the method when the network cannot be connected).

Second, install gcc directly, the first is to install via rpm (there are many dependencies, which is very cumbersome); the second is to install via gcc compressed package.

Only one way of my success is described here. Other ways can be searched. There are many articles describing it.

1. Install yum, replace with yum in CentOS, install through yum install gcc, In this way, make sure that the server can access the Internet

a. Back up the original yum

b. Delete red hat yum source

c. Download the new yum package, because it is red hat 7 to install the yum source of CentOS 7 version, the version must be corresponding, which can avoid a lot of trouble
Go to http://mirrors.163.com/centos/7/os/x86_64/Packages/ and download the following files
Download: yum-metadata-parser-1.1.4-10.el7.x86_64.rpm
yum-3.4.3-154.el7.centos.noarch.rpm
yum-plugin-fastestmirror-1.1.31-42.el7.noarch.rpm
python-iniparse-0.4-9.el7.noarch.rpm
Or order to download directly:
d. Install the new yum package
After installation, you can view it through commands:

If an error is reported about missing packages, you can copy the package name to http://mirrors.163.com/centos/7/os/x86_64/Packages/ to find the corresponding package, and download and install it.

For example: the python-urlgrabber package may be missing, download and install this package first.

Источник

💄 Установка GCC и средста разработки на RHEL 8 / CentOS 8

Как мне установить Инструменты разработки на RHEL / CentOS 8 ?

Дистрибутивы на основе RHEL предназначены для предприятий и запуска критически важных приложений.

Это самая стабильная и безопасная серверная операционная система.

По соображениям безопасности и производительности ОС часто поставляются с меньшим количеством предварительно установленных пакетов.

Если вы хотите заниматься разработкой или создавать приложения с открытым исходным кодом на RHEL / CentOS 8, вам необходимо установить инструменты разработки, которые включают в себя следующие инструменты.

autoconf
automake
gcc
gcc-c++
bison
flex
binutils
gdb
glibc-devel
libtool
make
pkgconf
pkgconf-m4
pkgconf–pkg-config
redhat-rpm-config
rpm-build
rpm-sign
strace

Перечислите группы пакетов на CentOS / RHEL 8

Введите следующую команду dnf, чтобы получить список групп пакетов, доступных на CentOS / RHEL 8.

Вы можете передать параметр summary , чтобы просмотреть количество установленных групп, доступных групп и т.д.

Установите GCC и средства разработки на сервере CentOS / RHEL 8

Следующая команда используется для установки GCC и средств разработки на сервере CentOS / RHEL 8.

Вы можете просмотреть информацию о группе пакетов Development Tools

Проверьте установку, проверив места расположения инструментов.

Проверьте установленную версию GCC.

Удаление GCC и средств разработки на сервере CentOS / RHEL 8

Ниже приведена команда, используемая для удаления группы пакетов в CentOS / RHEL 8.

Будьте внимательны к дереву зависимостей, чтобы не сломать другие системные пакеты.

Тестовый компилятор GCC

Давайте создадим программу Hello World, чтобы увидеть, правильно ли она компилируется.

Скомпилируйте код с GCC.

Запустите программу, чтобы увидеть, печатает ли она Hello, world на консоли!

Благодарим Вас за установку GCC и средств разработки на RHEL / CentOS 8 с помощью нашего руководства.

Вы можете проверить другие руководства RHEL / CentOS 8, доступные в нашем блоге.

Источник

Red Hat Customer Portal

Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

Red Hat Training

A Red Hat training course is available for Red Hat Developer Toolset

Chapter 2. GNU Compiler Collection (GCC)

The GNU Compiler Collection , commonly abbreviated GCC , is a portable compiler suite with support for a wide selection of programming languages.

Red Hat Developer Toolset is distributed with GCC 7.3.1 . This version is more recent than the version included in Red Hat Enterprise Linux and provides a number of bug fixes and enhancements.

2.1. GNU C Compiler

2.1.1. Installing the C Compiler

In Red Hat Developer Toolset, the GNU C compiler is provided by the devtoolset-7-gcc package and is automatically installed with devtoolset-7-toolchain as described in Section 1.5, “Installing Red Hat Developer Toolset”.

2.1.2. Using the C Compiler

To compile a C program on the command line, run the gcc compiler as follows:

This creates a binary file named output_file in the current working directory. If the -o option is omitted, the compiler creates a file named a.out by default.

When you are working on a project that consists of several source files, it is common to compile an object file for each of the source files first and then link these object files together. This way, when you change a single source file, you can recompile only this file without having to compile the entire project. To compile an object file on the command line,:

This creates an object file named object_file . If the -o option is omitted, the compiler creates a file named after the source file with the .o file extension. To link object files together and create a binary file:

Note that you can execute any command using the scl utility, causing it to be run with the Red Hat Developer Toolset binaries used in preference to the Red Hat Enterprise Linux system equivalent. This allows you to run a shell session with Red Hat Developer Toolset gcc as default:

To verify the version of gcc you are using at any point:

Red Hat Developer Toolset’s gcc executable path will begin with /opt . Alternatively, you can use the following command to confirm that the version number matches that for Red Hat Developer Toolset gcc :

Example 2.1. Compiling a C Program on the Command Line

Consider a source file named hello.c with the following contents:

Compile this source code on the command line by using the gcc compiler from Red Hat Developer Toolset:

This creates a new binary file called hello in the current working directory.

2.1.3. Running a C Program

When gcc compiles a program, it creates an executable binary file. To run this program on the command line, change to the directory with the executable file and run it:

Example 2.2. Running a C Program on the Command Line

Assuming that you have successfully compiled the hello binary file as shown in Example 2.1, “Compiling a C Program on the Command Line”, you can run it by typing the following at a shell prompt:

Читайте также: Как открыть wine linux

2.2. GNU C++ Compiler

2.2.1. Installing the C++ Compiler

In Red Hat Developer Toolset, the GNU C++ compiler is provided by the devtoolset-7-gcc-c++ package and is automatically installed with the devtoolset-7-toolchain package as described in Section 1.5, “Installing Red Hat Developer Toolset”.

2.2.2. Using the C++ Compiler

To compile a C++ program on the command line, run the g++ compiler as follows:

This creates a binary file named output_file in the current working directory. If the -o option is omitted, the g++ compiler creates a file named a.out by default.

This creates an object file named object_file . If the -o option is omitted, the g++ compiler creates a file named after the source file with the .o file extension. To link object files together and create a binary file:

To verify the version of g++ you are using at any point:

Red Hat Developer Toolset’s g++ executable path will begin with /opt . Alternatively, you can use the following command to confirm that the version number matches that for Red Hat Developer Toolset g++ :

Example 2.3. Compiling a C++ Program on the Command Line

Consider a source file named hello.cpp with the following contents:

Compile this source code on the command line by using the g++ compiler from Red Hat Developer Toolset:

This creates a new binary file called hello in the current working directory.

2.2.3. Running a C++ Program

When g++ compiles a program, it creates an executable binary file. To run this program on the command line, change to the directory with the executable file and run it:

Example 2.4. Running a C++ Program on the Command Line

Assuming that you have successfully compiled the hello binary file as shown in Example 2.3, “Compiling a C++ Program on the Command Line”, you can run it:

2.2.4. C++ Compatibility

All compilers from Red Hat Enterprise Linux versions 5, 6, and 7 and from Red Hat Developer Toolset versions 1, 2, 3, 4, and 6 in any -std mode are compatible with any other of those compilers in C++98 mode.

A compiler in C++11 or C++14 mode is only guaranteed to be compatible with another compiler in C++11 or C++14 mode if they are from the same release series (for example from Red Hat Developer Toolset 6.x).

All compatibility information mentioned in this section is relevant only for Red Hat-supplied versions of the GCC C++ compiler.

2.2.4.1. C++ ABI

Any C++98-compliant binaries or libraries built explicitly with -std=c++98 or -std=gnu++98 can be freely mixed with binaries and shared libraries built by the Red Hat Enterprise Linux 5, 6 or 7 system toolchain GCC. Red Hat recommends use of the -std=c++98 or -std=gnu++98 modes for production software development.

The default language standard setting for Red Hat Developer Toolset is C++14 with GNU extensions, equivalent to explicitly using option -std=gnu++14 .

Using and mixing the C++11, C++14, and C++17 language versions is supported in Red Hat Developer Toolset only when all C++ objects compiled with the respective flag have been built using the same major version of GCC. As later major versions of Red Hat Developer Toolset may use a later major release of GCC, forward-compatibility of objects, binaries, and libraries built with the options -std=c++11 , -std=gnu++11 , -std=c++14 , -std=gnu++14 , -std=c++17 , and -std=gnu++17 options cannot be guaranteed, and so is not supported.

Use of C++11, C++14 and C++17 features in your application requires careful consideration of the above ABI compatibility information.

The mixing of objects, binaries and libraries, built by the Red Hat Enterprise Linux 6 or 7 system toolchain GCC using the -std=c++0x or -std=gnu++0x flags, with those built with the -std=c++11 or -std=gnu++11 or -std=c++14 or -std=gnu++14 or -std=c++17 or -std=gnu++17 flags using the GCC in Red Hat Developer Toolset is explicitly not supported.

Aside from the C++11, C++14 and C++17 ABI, discussed above, the Red Hat Enterprise Linux Application Compatibility Specification is unchanged for Red Hat Developer Toolset. When mixing objects built with Red Hat Developer Toolset with those built with the Red Hat Enterprise Linux 6 or 7 toolchain (particularly .o / .a files), the Red Hat Developer Toolset toolchain should be used for any linkage. This ensures any newer library features provided only by Red Hat Developer Toolset are resolved at link-time.

A new standard mangling for SIMD vector types has been added to avoid name clashes on systems with vectors of varying lengths. The compiler in Red Hat Developer Toolset uses the new mangling by default. It is possible to use the previous standard mangling by adding the -fabi-version=2 or -fabi-version=3 options to GCC C++ compiler calls. To display a warning about code that uses the old mangling, use the -Wabi option.

On Red Hat Enterprise Linux 7, the GCC C++ compiler still uses the old mangling by default, but emits aliases with the new mangling on targets that support strong aliases. It is possible to use the new standard mangling by adding the -fabi-version=4 option to compiler calls. To display a warning about code that uses the old mangling, use the -Wabi option.

On Red Hat Enterprise Linux 6, the GCC C++ compiler supports only the previous standard mangling.

2.3. GNU Fortran Compiler

2.3.1. Installing the Fortran Compiler

In Red Hat Developer Toolset, the GNU Fortran compiler is provided by the devtoolset-7-gcc-gfortran package and is automatically installed with devtoolset-7-toolchain as described in Section 1.5, “Installing Red Hat Developer Toolset”.

2.3.2. Using the Fortran Compiler

To compile a Fortran program on the command line, run the gfortran compiler as follows:

This creates a binary file named output_file in the current working directory. If the -o option is omitted, the compiler creates a file named a.out by default.

To verify the version of gfortran you are using at any point:

Red Hat Developer Toolset’s gfortran executable path will begin with /opt . Alternatively, you can use the following command to confirm that the version number matches that for Red Hat Developer Toolset gfortran :

Example 2.5. Compiling a Fortran Program on the Command Line

Consider a source file named hello.f with the following contents:

Compile this source code on the command line by using the gfortran compiler from Red Hat Developer Toolset:

This creates a new binary file called hello in the current working directory.

2.3.3. Running a Fortran Program

When gfortran compiles a program, it creates an executable binary file. To run this program on the command line, change to the directory with the executable file and run it:

Example 2.6. Running a Fortran Program on the Command Line

Assuming that you have successfully compiled the hello binary file as shown in Example 2.5, “Compiling a Fortran Program on the Command Line”, you can run it:

2.4. Specifics of GCC in Red Hat Developer Toolset

Static linking of libraries

Certain more recent library features are statically linked into applications built with Red Hat Developer Toolset to support execution on multiple versions of Red Hat Enterprise Linux. This creates an additional minor security risk as standard Red Hat Enterprise Linux errata do not change this code. If the need arises for developers to rebuild their applications due to this risk, Red Hat will communicate this using a security erratum.

Because of this additional security risk, developers are strongly advised not to statically link their entire application for the same reasons.

Specify libraries after object files when linking

In Red Hat Developer Toolset, libraries are linked using linker scripts which might specify some symbols through static archives. This is required to ensure compatibility with multiple versions of Red Hat Enterprise Linux. However, the linker scripts use the names of the respective shared object files. As a consequence, the linker uses different symbol handling rules than expected, and does not recognize symbols required by object files when the option adding the library is specified before options specifying the object files:

Using a library from the Red Hat Developer Toolset in this manner results in the linker error message undefined reference to symbol . To prevent this problem, follow the standard linking practice, and specify the option adding the library after the options specifying the object files:

Note that this recommendation also applies when using the base Red Hat Enterprise Linux version of GCC .

2.5. Additional Resources

A detailed description of the GNU Compiler Collections and its features is beyond the scope of this book. For more information, see the resources listed below.

Installed Documentation

gcc (1) — The manual page for the gcc compiler provides detailed information on its usage; with few exceptions, g++ accepts the same command line options as gcc . To display the manual page for the version included in Red Hat Developer Toolset:

gfortran (1) — The manual page for the gfortran compiler provides detailed information on its usage. To display the manual page for the version included in Red Hat Developer Toolset:

C++ Standard Library Documentation — Documentation on the C++ standard library can be optionally installed:

Источник

Red hat enterprise linux install gcc

GCC 8.2 now GA for Red Hat Enterprise Linux

About Red Hat Developer Toolset

New features in Developer Toolset 8: