Bash script to install gcc 4.9.1 and boost 1.55.0 on CentOS 6.x, CentOS 5.x and Mac OS X 10.9

The bld.sh script provided installs gcc 4.9.1 and boost 1.55.0 on CentOS 6.x, CentOS 5.x and Mac OS X for testing. It is another entry in my continuing series of releases for different versions of g++. Hopefully this will make it easier for folks that want to experiment with this version of the GNU C++ compiler.

This script is also available on github: https://github.com/jlinoff/gcc-4.9.1-boost-1.55.

There is also a very simple Makefile: http://projects.joelinoff.com/gcc-4.9.1/Makefile that is not required but that I found useful.

This text version is also available so that you can cut-n-paste from a web page: http://projects.joelinoff.com/gcc-4.9.1/bld.sh.txt.

Please note that this is not a product. It is simply my best attempt to get it working in my development environments. For example, it does not check for packages because I try to build it on different systems that have different package managers (yum, apt, port, etc.). What this means is that if it doesn’t work for you, you will have to do some debugging. If you find a problem, please post a fix in the comment section here so that others can benefit from it.

1 Download and Install It

Here are the steps to download and install it. Root access is not required unless you need to install support packages.

$ # Download and install it.
$ mkdir /shared/tools/gcc/4.9.1
$ cd /shared/tools/gcc/4.9.1
$ wget http://projects.joelinoff.com/gcc-4.9.1/bld.sh
$ chmod a+x bld.sh

$ # Optionally there is also a very simple Makefile.
$ wget http://projects.joelinoff.com/gcc-4.9.1/Makefile

$ # bld.sh doesn't check for packages
$ # This is one that I needed.
$ # if not installed you will see a missing gnu/stabs-32.h error late in the process.
$ sudo yum install -y glibc-devel.i686
<output snipped>

$ # I also had to install texinfo, you may have to install others.
$ sudo yum install -y texinfo
<output snipped>

$ # You can run bld.sh directly or you can simply type "make" if you downloaded
$ # the Makefile.
$ ./bld.sh 2>&1| tee bld.log

$ # Download and install it.

$ mkdir /shared/tools/gcc/4.9.1

$ cd /shared/tools/gcc/4.9.1

$ wget http://projects.joelinoff.com/gcc-4.9.1/bld.sh

$ chmod a+x bld.sh

$ # Optionally there is also a very simple Makefile.

$ wget http://projects.joelinoff.com/gcc-4.9.1/Makefile

$ # bld.sh doesn't check for packages

$ # This is one that I needed.

$ # if not installed you will see a missing gnu/stabs-32.h error late in the process.

$ sudo yum install -y glibc-devel.i686

$ # I also had to install texinfo, you may have to install others.

$ sudo yum install -y texinfo

$ # You can run bld.sh directly or you can simply type "make" if you downloaded

$ # the Makefile.

$ ./bld.sh 2>&1| tee bld.log

The build process can take a long time depending on the speed of your CPU(s) and disks. On my test system it took more than 5 hours.

If the process fails it is most likely because packages are missing on the system.

If a problem does occur, install the package, then delete the src and bld directories and try again. If you have installed the option Makefile you can type “make clean” and then “make”.

The rtf (release to field) directory contains the releases for each package.

2 How to Use the Compiler

This section shows how to compile, link and execute a simple program using the newly installed compiler by setting up your environment properly.

// Simple test program
#include <iostream>
#include <boost/algorithm/string.hpp>
using namespace std;
using namespace boost;
int main()
{
  string s1(" hello world! ");
  cout << "value      : '" << s1 << "'" <<endl;

  to_upper(s1);
  cout << "to_upper() : '" << s1 << "'" <<endl;

  trim(s1);
  cout << "trim()     : '" << s1 << "'" <<endl;

  return 0;
}

// Simple test program

#include <iostream>

#include <boost/algorithm/string.hpp>

using namespace std;

using namespace boost;

int main()

{

string s1(" hello world! ");

cout << "value : '" << s1 << "'" <<endl;

to_upper(s1);

cout << "to_upper() : '" << s1 << "'" <<endl;

trim(s1);

cout << "trim() : '" << s1 << "'" <<endl;

return 0;

}

You compile, link and run it as follows:

#!/bin/bash
# This script sets the environment to use the newly installed compiler.
# It compiles, links and runs a small test program.

# Setup the environment.
MY_GXX_HOME="/shared/tools/gcc/4.9.1/rtf"
export PATH="${MY_GXX_HOME}/bin:${PATH}"
export LD_LIBRARY_PATH="${MY_GXX_HOME}/lib:${MY_GXX_HOME}/lib64:${LD_LIBRARY_PATH}"
export LD_RUN_PATH="${MY_GXX_HOME}/lib:${MY_GXX_HOME}/lib64:${LD_LIBRARY_PATH}"

# Compile and link.
g++ -O3 -std=c++11 -Wall -o test.exe test.cc

# Run.
./test.exe
# Expected output
# value      : ' hello world! '
# to_upper() : ' HELLO WORLD! '
# trim()     : 'HELLO WORLD!'

#!/bin/bash

# This script sets the environment to use the newly installed compiler.

# It compiles, links and runs a small test program.

# Setup the environment.

MY_GXX_HOME="/shared/tools/gcc/4.9.1/rtf"

export PATH="${MY_GXX_HOME}/bin:${PATH}"

export LD_LIBRARY_PATH="${MY_GXX_HOME}/lib:${MY_GXX_HOME}/lib64:${LD_LIBRARY_PATH}"

export LD_RUN_PATH="${MY_GXX_HOME}/lib:${MY_GXX_HOME}/lib64:${LD_LIBRARY_PATH}"

# Compile and link.

g++ -O3 -std=c++11 -Wall -o test.exe test.cc

# Run.

./test.exe

# Expected output

# value : ' hello world! '

# to_upper() : ' HELLO WORLD! '

# trim() : 'HELLO WORLD!'

3 Disk Space Requirements

You will need about 5.5GB to download and build all of the packages. Once the build is finished you can reclaim most of the space because the released files only require about 600 MB. Here is the breakdown:

$ # This was on my Mac
$ cd /shared/tools
$ du -s -h gcc/4.9.1
5.5G    gcc/4.9.1

$ du -s -h gcc/4.9.1/*
187M    gcc/4.9.1/archives
2.1G    gcc/4.9.1/bld
28K     gcc/4.9.1/bld.sh
18M     gcc/4.9.1/logs
4.0K    gcc/4.9.1/Makefile
595M    gcc/4.9.1/rtf
2.6G    gcc/4.9.1/src

$ # This was on my Mac

$ cd /shared/tools

$ du -s -h gcc/4.9.1

5.5G gcc/4.9.1

$ du -s -h gcc/4.9.1/*

187M gcc/4.9.1/archives

2.1G gcc/4.9.1/bld

28K gcc/4.9.1/bld.sh

18M gcc/4.9.1/logs

4.0K gcc/4.9.1/Makefile

595M gcc/4.9.1/rtf

2.6G gcc/4.9.1/src

Note that the logs directory exists because I used the “make” command instead of running blds.sh directly.

Once it is built you can remove everything except the contents of the rtf directory tree to save disk space.

4 Packages

This is the list of packages that are installed in the release area.

Package	Version	Web Site
binutils	2.24	http://ftp.gnu.org/gnu/binutils
boost	1.55.0	http://sourceforge.net/projects/boost/files/boost
cloog	0.18.1	http://www.bastoul.net/cloog”>http://www.bastoul.net/cloog
gcc	4.9.1	http://ftp.gnu.org/gnu/gcc
gmp	6.0.0a	http://gmplib.org/
libiconv	1.14	http://ftp.gnu.org/pub/gnu/libiconv
mpc	1.0.2	http://www.multiprecision.org/mpc
mpfr	3.1.2	http://www.mpfr.org
ppl	1.1	http://bugseng.com/products/ppl

5 Tested Platforms

These are the platforms that I actually tested the installation on.

Distro	Version	Arch	Status	Date	Notes
CentOS	5.5	x86_64	Passed	2014-06-26
CentOS	6.3	x86_64	Passed	2014-06-27	Had to manually install the glibc_devel.i686 and texinfo packages.
CentOS	6.5	x86_64	Passed	2014-06-26	Had to manually install the glibc_devel.i686 and texinfo packages.
MAC OS X	10.9.3	x86_64	Passed	2014-06-26	Used macports for setting up the environment.

Unfortunately, I do not have the bandwidth to try to get this to work on other distros (even though I have several Ubuntu boxes at hand) but it should be fairly straightforward to port because it does not rely on distro specific package management.

If you port it to another distro, please send me the changes to that I can incorporate them.

Enjoy!

One thought on “Bash script to install gcc 4.9.1 and boost 1.55.0 on CentOS 6.x, CentOS 5.x and Mac OS X 10.9”

jlinoff says:

September 17, 2014 at 1:48 pm

User “jeaye” posted this workaround for installation problems encountered:

I’d like to mention that I had to unset some
environment variables in order to get GCC to build properly.

unset LIBRARY_PATH CPATH C_INCLUDE_PATH PKG_CONFIG_PATH
CPLUS_INCLUDE_PATH INCLUDE

I found this solution here:
http://stackoverflow.com/questions/12255058/g-4-7-1-compilation-error-conflicting-types-for-strsignal

Perhaps your script should unset these by default.

That is a great idea. I will do that in the next release.

Log in to Reply