Getting + installing gcc/g++ 4.9 on Ubuntu? [duplicate]

Solution 1:

You can install close to upstream version of GCC from Ubuntu Toolchain PPA: https://wiki.ubuntu.com/ToolChain#PPA_packages

sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get install g++-4.9

Tested on Ubuntu 14.04.

Solution 2:

Intro

teach a man to fish etc. etc.

How to build the source package and serve it from a local repository in an apt-friendly way. This will work on any distribution provided that dependencies can be satisfied/ This method does not require you to install build-deps for every package and polluting your machine with extraneous packages, this will let you keep up with packages as they get updated in debian experimental. It takes just a few minutes to do this once, and then can be reused to rebuild any package you need without relying on other people to package ppa for you or downloading a bunch of different .debs

The benefit of building vs. pulling raw .debs from debian is that this will build packages against the packages in your distribution which may differ in version/revision from what is used as build-dependencies for the debian distribution. This is more-or-less the process for backporting packages. You can also use any ubuntu distribution to build packages targeted at any other distribution (target in this case means build against the standard repository packages) with no hassle.

Basic-How-to-Build-a-deb

(not for ppa uploading - this has beurocratic requirements from launchpad

Probably-required: packaging-dev (pulls build-essential pubilder ubuntu-dev-tools among others)

1. Set up pbuilder (this lets you build a package in a chroot without polluting your system with build-dependency packages)

   • sudo pbuilder create,
   • if you want to build for a specific distribution, (pbuilder uses the build system release in a chroot) you can use pbuilder-dist [precise/oneric/trusy/etc...] create

2. Get debian source

   • pull-debian-source gcc-4.9 [4.9.0-6] specific debian revision is optional, but can be useful if you want to pull experimental/unstable/testing/stable revisions
   • you can also pull from specific ubuntu distros by adding them to sources.list as a deb-src and using sudo apt-get src

3. Build Package

   • sudo pbuilder build gcc-4.9_4.9.0-6.dsc
   • In the files downloaded there is a .dsc file, for the most recent gcc it is gcc-4.9_4.9.0-6.dsc which is a package descriptor file. .orig.tar.[gz/xz] is the source tarball.

4. Create local Apt-repository

   • mkdir /convenient/place/for/repo
   • cp /var/cache/pbuilder/result/* /path/to/repo
   • (assuming you are in repo dir) apt-ftp archive packages . > Packages
   • (one of many ways to do this) sudo echo "deb [trusted=yes] file:/local/repo/Packages ./" > /etc/apt/sources.list.d/gcc-repo.list
   • Note you can also do this step with .debs downloaded from anywhere (skip step 1-3)

5. Install

   • apt-get update; apt-get install gcc-4.9 g++-4.9

Extra Tricks

Easy backporting Dependencies

Using self-compiled packages to satisfy dependencies when building packages. (I have it set up with folders ~/pbuilder ~/pbuilder/precise_local (local package repo for precise) and ~/pbuilder/precise_hooks (for hook scripts) )

Add the following to your ~/.pbuilderrc

OTHERMIRROR="deb [trusted=yes] file:///home/user/pbuilder/precise_local ./"

BINDMOUNTS="/home/user/pbuilder/precise_local" 

HOOKDIR="/home/user/pbuilder/precise_hooks"

EXTRAPACKAGES="apt-utils"

in precise_hooks create a file D05local (in typical unix/linux fashion, prefix D tells when script is hooked 05 is self-imposed name-ordering and local is just the name, if you only have one hook it is not important what its called as long as D is the prefix

the script is a one-liner

(cd /home/user/pbuilder/precise_local ; apt-ftparchive packages . > Packages)

Now any packages placed in precise_local will satisfy build-depends. This is supremely useful to construct a dependency tree locally when back-porting packages that have dependencies that also need backporting

The VM solution

To do this in an even cleaner way, use a VM image or LXC container to jail this mess.

Applying custom patches

you can apply custom patches in most debian packages using quilt, quilt patches can use diffs from most VCSs (see : using quilt )

There is an additional step, you must rebuild the .dsc and .debian.tar.gz. Cleanest-way I know is bzr-builddeb it has the highest success rate IMHO (compared to git-build-package and other helper scripts) and is much cleaner than calling debuild directly (bzr= bazaar canonical's VCS)

1. sudo apt-get install bzr-builddeb
2. (assuming .orig.tar.gz is extracted and .debian.tar.gz is extracted and place in it
   • bzr init
   • bzr add
   • bzr commit
3. (OPTIONAL)
   • modify debian/changelog
   • add patch to debian/patches/ and modify debian/patches/series (quilt also has utility to add patches or for you to modify on the fly, see documentation)
   • bzr add debian/
   • bzr commit
4. bzr builddeb -- -S -us -uc This rebuilds the source file and leaves it unsigned (gpg signing required for PPA/distro uploading, but not for private local repos)
5. cd ../build-area/ Continue from Step 3 above.

Steps 1-4 here are pretty much what you need to upload to a PPA (they do not take binary files), but you require some steps to satisfy launchpad bureaucracy (this answer provides a explanation, this one has some links)

Solution 3:

install

sudo su -
apt-get install build-essential
add-apt-repository ppa:ubuntu-toolchain-r/test
apt-get update
apt-get install gcc-4.9 g++-4.9 cpp-4.9

after that if you check the version of gcc you will find the old version

gcc --version

so we can fix it with simple symbolic

cd /usr/bin
rm gcc g++ cpp
ln -s gcc-4.9 gcc
ln -s g++-4.9 g++
ln -s cpp-4.9 cpp

or

// Actually i tried the symbolic & i know this will work but you may use the symbolic to get it without problems // please correct me if I am wrong

update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.9 40 --slave /usr/bin/gcc gcc /usr/bin/gcc-4.9
update-alternatives --config gcc
update-alternatives --install /usr/bin/cpp cpp /usr/bin/cpp-4.9 40 --slave /usr/bin/cpp cpp /usr/bin/cpp-4.9
update-alternatives --config cpp
update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.9 40 --slave /usr/bin/g++ g++ /usr/bin/g++-4.9
update-alternatives --config g++

or

/usr/bin/gcc4.9 filename.c

gcc-4.9 is just like the gcc-4.8 "ubuntu 14.04 gcc" it is not a big deference