Skip to content

erikw/ewxb-gcc-cross-compiler-builder

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

21 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ewxb - Erik Westrup's GCC cross-compiler builder

SLOC Top programming languages used

This is a script documenting the steps and phases take when I compiled a GCC cross toolchain for GCC 4.9 head (with Go support). Building a cross-compiler is complex due to dependencies so a lot of bootstrapping has to be done. This script is inspired by Jim Blandy's excellent eglibc cross-compiling guide posted at eglibc's mailinglist at [patches] Cross-building instructions.

This script can serve as a starting point for those who want to build a x-toolchain from scratch. Don't expect it to work in directly as it's tailored for my setup. Instead you can re-use the phases and modify the script with parameters that you need. The last phases adds Go support, which is easy to comment out if you're only interested in a C/C++ compiler.

My setup was:

  • Host/Build system: Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux
  • Target: mips
  • gcc: 4.9.0
  • glibc: 2.19
  • binutils: 2.24

The scripts makes it easy to run specific phases (or range of phases) so that you easly can tweak a failing phase and continue with the ones that follows when you have got one phase to work. Make sure to edit x_environment.sh to the right versions of the packages and build paths to use.

For any details, simply read the sauce.

More info about using Go with a gccgo cross-compiler can be found at the go-wiki.

Resulting x-compiler tools

The sweet result after playing some Rube Goldberg trickery games.

About

A script for building a full GCC + glibc toolchain from scratch (with Go support via gccgo) in multiple stages.

Topics

Resources

License

Stars

Watchers

Forks

Languages

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy