# Revision history [back]

Hi! I hope this may help you, so there we go. As seeing in the wiki of gcc here http://gcc.gnu.org/wiki/InstallingGCC the /configure inside the source code is not supported so this is what we are going to do.
First we create a new directory
1.- mkdir gcc-src
2.- cd gcc-src
Now we should unzip that .tar.gz file
3.- tar xzf path-of-tar-file/gcc-version.tar.gz
So as GCC has some prerequisites we should run instead of "/configure" inside of our source code directory
this will download and untar inside the source code directory MPR, MPC and GMP
Now here is the deal, we should create a mirror-directory (just for call it something) so we get out of our source-code-directory and make a new one right next to our source code.
5.- mkdir gcc-build
and move into our new directory
6.- cd gcc-build
In this new directory we can run the /configure so we create a path to our source code folder and run the /configure
7.- path/gcc-src/gcc-version/configure *
this would create a "make" file in our gcc-build directory so we just run make inside the directory
*
8.- make

finally we install gcc
9.- make install
And I think that would be pretty much about it =) , this way you wont be touching the source-code-directory by building in the mirror-directory. And of course can delete that gcc-build and make another one just by following those steps.

Hi! I hope this may help you, so there we go. As seeing in the wiki of gcc here http://gcc.gnu.org/wiki/InstallingGCC the /configure inside the source code is not supported so this is what we are going to do.
First we create a new directory
1.- mkdir gcc-src
2.- cd gcc-src
Now we should unzip that .tar.gz file
3.- tar xzf path-of-tar-file/gcc-version.tar.gz
So as GCC has some prerequisites we should run instead of "/configure" inside of our source code directory
this will download and untar inside the source code directory MPR, MPC and GMP
Now here is the deal, we should create a mirror-directory (just for call it something) so we get out of our source-code-directory and make a new one right next to our source code.
5.- mkdir gcc-build
and move into our new directory
6.- cd gcc-build
In this new directory we can run the /configure so we create a path to our source code folder and run the /configure
7.- path/gcc-src/gcc-version/configure * path/gcc-src/gcc-version/configure
this would create a "make" file in our gcc-build directory so we just run make inside the directory
*
8.- make
finally we install gcc
9.- make install
And I think that would be pretty much about it =) , this way you wont be touching the source-code-directory by building in the mirror-directory. And of course can delete that gcc-build and make another one just by following those steps.

Hi! I hope this may help you, so there we go. As seeing in the wiki of gcc here http://gcc.gnu.org/wiki/InstallingGCC the /configure inside the source code is not supported so this is what we are going to do.
First we create a new directory
1.-

mkdir gcc-src  2.- gcc-src
cd gcc-src gcc-src


Now we should unzip that .tar.gz file
3.-

tar xzf path-of-tar-file/gcc-version.tar.gz  path-of-tar-file/gcc-version.tar.gz


So as GCC has some prerequisites we should run instead of "/configure" inside of our source code directory
this

./contrib/download_prerequisites


This will download and untar inside the source code directory MPR, MPC and GMP
Now here is the deal, we should create a mirror-directory (just for call it something) so we get out of our source-code-directory and make a new one right next to our source code.
5.-

mkdir gcc-build  gcc-build


and move into our new directory
6.-

cd gcc-build  gcc-build


In this new directory we can run the /configure so we create a path to our source code folder and run the /configure
7.- path/gcc-src/gcc-version/configure

path/gcc-src/gcc-version/configure


this would create a "make" file in our gcc-build directory so we just run make inside the directory
8.- make

make


finally we install gcc
9.-

make install  install


And I think that would be pretty much about it =) , this way you wont be touching the source-code-directory by building in the mirror-directory. And of course can delete that gcc-build and make another one just by following those steps.