972
edits
[unchecked revision] | [unchecked revision] |
m (Added package names for GNU Texinfo for various Linux distributions) |
m (Replace deprecated enclose attributes) |
||
(57 intermediate revisions by 29 users not shown) | |||
Line 1:
{{Rating|1}}
<noinclude>'''Note that this article is meant to be included into the [[GCC Cross-Compiler]] and [[Building GCC]] as they share this common section.'''</noinclude>
The GNU Compiler Collection is an advanced piece of software with dependencies. You need the following in order to build GCC:
* A Unix-like environment (Windows users can use the Windows Subsystem for Linux or Cygwin)
* Enough memory and hard disk space (it depends, 256 MiB will not be enough).
* GCC (existing release you wish to replace), or another system C compiler
* G++ (if building a version of GCC >= 4.8.0), or another system C++ compiler
*
*
* Flex
*
*
*
* Texinfo
* ISL (optional)
=== Installing Dependencies ===
{| {{wikitable}}
|-
! ↓ Dependency / OS →
| Source Code
| Debian (Ubuntu, Mint, WSL, ...)
| Gentoo
| Fedora
| Cygwin
| OpenBSD
| Arch
|-
|How to install
|Normally
|'''<tt>sudo apt install</tt> ''foo'''''
|'''<tt>sudo emerge --ask</tt> ''foo'''''
|'''<tt>sudo dnf install</tt> ''foo'''''
|Cygwin GUI setup
|'''<tt>doas pkg_add</tt> ''foo'''''
|'''<tt>pacman -Syu</tt> ''foo'''''
|-
|Compiler
|N/A
|'''<tt>build-essential</tt>'''
|'''<tt>sys-devel/gcc</tt>'''
|'''<tt>gcc gcc-c++</tt>'''
|'''<tt>mingw64-x86_64-gcc-g++</tt>''' / '''<tt>mingw64-i686-gcc-g++</tt>'''
|Preinstalled
|'''<tt>base-devel</tt>'''
|-
|Make
|N/A
|'''<tt>build-essential</tt>'''
|'''<tt>dev-build/make</tt>'''
|'''<tt>make</tt>'''
|'''<tt>make</tt>'''
|Preinstalled
|'''<tt>base-devel</tt>'''
|-
|[https://www.gnu.org/software/bison/ Bison]
|[https://ftp.gnu.org/gnu/bison/]
|'''<tt>bison</tt>'''
|'''<tt>sys-devel/bison</tt>'''
|'''<tt>bison</tt>'''
|'''<tt>bison</tt>'''
|?
|'''<tt>base-devel</tt>'''
|-
|[https://github.com/westes/flex Flex]
|[https://github.com/westes/flex/releases]
|'''<tt>flex</tt>'''
|'''<tt>sys-devel/flex</tt>'''
|'''<tt>flex</tt>'''
|'''<tt>flex</tt>'''
|?
|'''<tt>base-devel</tt>'''
|-
|[https://gmplib.org/ GMP]
|[https://ftp.gnu.org/gnu/gmp/]
|'''<tt>libgmp3-dev</tt>'''
|'''<tt>dev-libs/gmp</tt>'''
|'''<tt>gmp-devel</tt>'''
|'''<tt>libgmp-devel</tt>'''
|'''<tt>gmp</tt>'''
|'''<tt>gmp</tt>'''
|-
|MPC
|[https://ftp.gnu.org/gnu/mpc/]
|'''<tt>libmpc-dev</tt>'''
|'''<tt>dev-libs/mpc</tt>'''
|'''<tt>libmpc-devel</tt>'''
|'''<tt>libmpc-devel</tt>'''
|'''<tt>libmpc</tt>'''
|'''<tt>libmpc</tt>'''
|-
|[https://www.mpfr.org/ MPFR]
|[https://ftp.gnu.org/gnu/mpfr/]
|'''<tt>libmpfr-dev</tt>'''
|'''<tt>dev-libs/mpfr</tt>'''
|'''<tt>mpfr-devel</tt>'''
|'''<tt>libmpfr-devel</tt>'''
|'''<tt>mpfr</tt>'''
|'''<tt>mpfr</tt>'''
|-
|[https://www.gnu.org/software/texinfo/ Texinfo]
|[https://ftp.gnu.org/gnu/texinfo/]
|'''<tt>texinfo</tt>'''
|'''<tt>sys-apps/texinfo</tt>'''
|'''<tt>texinfo</tt>'''
|'''<tt>texinfo</tt>'''
|'''<tt>texinfo</tt>'''
|'''<tt>base-devel</tt>'''
|-
|[http://isl.gforge.inria.fr/ ISL] (Optional)
|[http://isl.gforge.inria.fr/]
|'''<tt>libisl-dev</tt>'''
|'''<tt>dev-libs/isl</tt>'''
|'''<tt>isl-devel</tt>'''
|'''<tt>libisl-devel</tt>'''
|N/A
|N/A
|}
You need to have Texinfo installed to build Binutils. You need to have GMP, MPC, and MPFR installed to build GCC. GCC optionally can make use of the ISL library.
For instance, you can install '''<tt>libgmp3-dev</tt>''' on Debian by running the shell command: '''<tt>sudo apt install libgmp3-dev</tt>'''
'''Note:''' Version 5.x (or later) of Texinfo is known to be incompatible with the current Binutils 2.23.2 release (and older). You can check your current version using <tt>makeinfo --version</tt>. If your version is too new and you encounter problems during the build, you will need to either use Binutils 2.24 release (or newer) or install an older version of Texinfo - perhaps through building from source - and add it to your <tt>PATH</tt> prior and during the Binutils build.
'''Note:''' GCC has dropped support for CLooG in the 5.x releases [https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=r5-2770-geae1a5d419d30e], and many distributions have dropped the CLooG package (e.g. Gentoo in December 2022).
'''Note:''' GCC requires at least ISL version 0.15.
'''Note:''' If you are using '''Cygwin''', it is recommended to install the <tt>'''libintl-devel'''</tt> package (I couldn't build a cross-compiler without this package)
=== Downloading the Source Code ===
Download the needed source code into a suitable directory such as <tt>$HOME/src</tt>:
* You can download the desired Binutils release by visiting the [https://gnu.org/software/binutils/ Binutils website] or directly accessing the [https://ftp.gnu.org/gnu/binutils/ GNU main mirror].
* You can download the desired GCC release by visiting the [https://gnu.org/software/gcc/ GCC website] or directly accessing the [https://ftp.gnu.org/gnu/gcc/ GNU main mirror].
'''Note:''' The versioning scheme used is that each fullstop separates a full number, i.e. Binutils 2.20.0 is newer than 2.9.0. This may be confusing, if you have not encountered this (quite common) versioning scheme yet, when looking at an alphanumerically sorted list of tarballs: The file at the bottom of the list is not the latest version! An easy way of getting the latest version is to sort by the last modified date and scrolling to the bottom.
=== Linux Users building a System Compiler ===
Your distribution may ship its own patched GCC and Binutils that is customized to work on your particular Linux distribution. You should be able to build a working cross-compiler using the above source code, but you might not be able to build a new system compiler for your current Linux distribution. In that case, try a newer GCC release or get the patched source code.
=== Gentoo Users ===
Gentoo offers [https://wiki.gentoo.org/wiki/Crossdev crossdev] to set up a cross-development toolchain:
emerge -av crossdev
crossdev --help
PORTDIR_OVERLAY="/usr/local/crossdev" crossdev --stage1 --binutils <binutils-version> --gcc <gcc-version> --target <target>
This will install a GCC cross-compiler into a "slot", i.e. alongside already-existing compiler versions. You can install several cross-compilers that way, simply by changing target designations. An unfortunate downside is that it will also pull in gentoo patches and pass additional configure options that differ from the official [[GCC Cross-Compiler]] setup, and they might behave differently.
After the compilation finishes successfully, your cross-compiler is callable via <target>-gcc. You can also use gcc-config to toggle between compiler versions should you need to do so. Don't replace your system compiler with a cross-compiler. The package manager will also suggest updates as soon as they become available.
You can uninstall the cross-compiler by calling ''crossdev --clean <target>''. Read the [https://wiki.gentoo.org/wiki/Cross_build_environment cross-development] document for additional information.
Note that the version numbers to binutils and gcc are ''Gentoo package versions'', i.e. there might be a suffix to the "official" (GNU) version that addresses additional patchsets supplied by the Gentoo maintainers. (For example, ''--binutils 2.24-r3 --gcc 4.8.3'' is the latest stable package pair at the time of this writing.) You can omit the version numbers to use the latest package available.
Portage uses overlays to store packages that are not part of the original package management. Crossdev needs one overlay where it can store its binutils and gcc packages before building them. You can configure one properly, or you can use PORTDIR_OVERLAY to point at where it should keep its package manager files. Using PORTDIR_OVERLAY is not a good idea with existing overlays, but by then you should know how you have personally set them up earlier anyway and how to do it properly. See [https://wiki.gentoo.org/wiki/Custom_repository#Crossdev].
===
The makefiles of
<syntaxhighlight lang="bash">
# This is only necessary for OS X users running 10.7 or below.
export CC=/usr/bin/gcc-4.2
Line 64 ⟶ 178:
export CPP=/usr/bin/cpp-4.2
export LD=/usr/bin/gcc-4.2
</syntaxhighlight>
You
'''Note for Lion users:''' If you're on Lion (or above) chances are that you don't have the "real"
'''Note for Maverick users:''' You can build binutils-2.24 and gcc-4.8.3 (possible other version) with Xcode 5.1.1. Note that building GCC with LLVM is not officially supported and may cause interesting bugs, if you are willing to take this risk and save time building host-gcc just to compile a cross-gcc, follow this.
Install GMP, MPFR, Mpc with [https://www.macports.org/ MacPorts].
sudo port install gmp mpfr libmpc
Line 86 ⟶ 201:
--with-gmp=/usr --with-mpc=/opt/local --with-mpfr=/opt/local
'''Note2:''' If you still have some errors, try making a case-sensitive APFS disk image using disk utility app and build from there
=== Windows Users ===
Windows users need to set up a Unix-like enviroment such as [[MinGW]] or [[Cygwin]]. It may well be worth looking into systems such as Linux and see if they fit your needs, as you commonly use a lot of Unix-like tools in operating systems development and this is much easier from a Unix-like operating system. '''If you have just installed the basic [[Cygwin]] package, you have to run the setup.exe again and install the following packages:''' GCC, G++, Make, Flex, Bison,
MinGW + MSYS is an option, and as it addresses the native Windows API instead of a POSIX emulation layer, results in a slightly faster toolchain. Some software packages will not build properly under MSYS as they were not designed for use with Windows. As far as this tutorial is concerned, everything that applies to Cygwin also applies to MSYS unless otherwise specified. Make sure you install the C and C++ compilers, and the MSYS Basic System.
The "Windows Subsystem for Linux (Beta)", released with the Windows 10 Anniversary update is also an option for using a cross compiler. (Tested 08/08/2016 with GCC 6.1.0 and Binutils 2.27) This cross-compiler works reasonably fast, although being in beta state, it may not be ideal permanent development platform.
'''Cygwin note:''' Cygwin includes your Windows <tt>%PATH%</tt> in its bash <tt>$PATH.</tt> If you were using DJGPP before, this could result in confusion as e.g. calling <tt>GCC</tt> on the Cygwin bash command line would still call the DJGPP compiler. After uninstalling DJGPP, you should delete the DJGPP environment variable and clear the <tt>C:\djgpp</tt> entry (or wherever you installed it) from your <tt>%PATH%</tt>. Likewise, it might be a bad idea to mix build environments in your system PATH variable.
'''MinGW note:''' Some MinGW-specific information on building a cross-toolchain can be found on the [http://www.mingw.org/wiki/HostedCrossCompilerHOWTO hosted cross-compiler how-to page] on the MinGW homepage.
'''Windows Subsystem for Linux (Beta) Note:''' You cannot have your cross compiler in the /mnt/c/ (or /mnt/"x") areas, as trying to compile your cross-compiler there will generate errors, whereas building to $HOME/opt/cross works perfectly. This is fixed with Windows Update KB3176929
=== OpenBSD Users ===
OpenBSD users might need to install "gcc" package from ports because base system's GCC is very outdated. If you want to build GCC, try to use the ports' version instead of the latest version available and apply all patches from ports to your build. Also, if the build fails during compiling lto-plugin, a temporary solution is to disable LTO altogether during configure stage of building GCC by adding <tt>--disable-lto</tt>
[[Category:Compilers]]
|