Package custom-cpp5: Information
Binary package: custom-cpp5
Version: 5.3.1-alt2.M70C.1
Architecture: x86_64
Build time: Apr 24, 2019, 06:05 PM in the task #218597
Source package: gcc5
Category: Development/C
Report package bugDownload: custom-cpp5-5.3.1-alt2.M70C.1.x86_64.rpm
Home page: http://gcc.gnu.org/
Summary: The GNU C-Compatible Compiler Preprocessor
Description:
Cpp is the GNU C-Compatible Compiler Preprocessor. The C preprocessor is a 'macro processor' which is used automatically by the C compiler to transform your program before actual compilation. It is called a macro processor because it allows you to define 'macros,' which are abbreviations for longer constructs. The C preprocessor provides four separate facilities that you can use as you see fit: * Inclusion of header files. These are files of declarations that can be substituted into your program. * Macro expansion. You can define 'macros,' which are abbreviations for arbitrary fragments of C code, and then the C preprocessor will replace the macros with their definitions throughout the program. * Conditional compilation. Using special preprocessing directives, you can include or exclude parts of the program according to various conditions. * Line control. If you use a program to combine or rearrange source files into an intermediate file which is then compiled, you can use line control to inform the compiler about where each source line originated. If you have multiple versions of the GNU Compiler Collection installed on your system, you may want to execute cpp-5 in order to explicitly use the GNU C Preprocessor version 5.3.1.
Maintainer: Alexey Appolonov
List of contributors:
Alexey Appolonov
Gleb Fotengauer-Malinovskiy
Dmitry V. Levin
Sergey Bolshakov
Kirill A. Shutemov
Alex V. Myltsev
Stanislav Ievlev
goldhead
Alexey Appolonov
Gleb Fotengauer-Malinovskiy
Dmitry V. Levin
Sergey Bolshakov
Kirill A. Shutemov
Alex V. Myltsev
Stanislav Ievlev
goldhead
Last changed
Nov. 8, 2018 Alexey Appolonov 5.3.1-alt2.M70C.1
- C7 custom port: + No Ada, no Fortran, no Java, no Go; + No gdb-plugin and no libcilkrts; + Libraries and most executables can be found only by absolute paths which include GCC version\marker, common libraries of all versions of the custom-gcc can be found in the same place; + custom libraries (such as custom-libstdc++6 and custom-libgcc1) should not be used in runtime (maintainers should set RPATH to use them in exceptional cases).
March 10, 2016 Gleb Fotengauer-Malinovskiy 5.3.1-alt3
- Moved liblto_plugin.so back into %_libexecdir. - Added executable bit to liblto_plugin.so. - Backported upstram fix: + Enable frame pointer for TARGET_64BIT_MS_ABI when stack is misaligned (ALT#31834).
Feb. 24, 2016 Gleb Fotengauer-Malinovskiy 5.3.1-alt2
- Moved liblto_plugin.so into %_libdir.