On 06/08/14 11:11, Syed Ahsan Ali Bokhari wrote:
I have set following paths in .bashrc to correspond to the latest
installation of gcc
export PATH=$PATH:/opt/gcc-4.9.1/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/gcc-4.9.1/lib:/opt/gcc-4.9.1/lib64
but still on run time the previous binaries/libraries are being found
[rcm@rcm ~]$ which gcc
/usr/bin/gcc
How to handle this?
PATH is usually read left to right, so you'd want to add your new path
to the beginning like so:
export PATH=/opt/gcc-4.9.1/bin:$PATH
Kyrill
On Wed, Aug 6, 2014 at 8:16 AM, Syed Ahsan Ali Bokhari
<ahsan.pmd@xxxxxxxxx> wrote:
Well explained Jonathan
Thanks
On Tue, Aug 5, 2014 at 10:10 PM, Jonathan Wakely <jwakely.gcc@xxxxxxxxx> wrote:
On 5 August 2014 17:54, Syed Ahsan Ali Bokhari wrote:
Yes I did that before, I removed the gcc and when I tried to build a
new gcc from source it crashed complaining that no C compiler is
present. Isn't it weird that installation of C compiler needs C
compiler as a pre-requisite.?
You don't need a compiler to install a C compiler, you need a compiler
to *compile* a C compiler, just like you need a compiler to compile
any program.
If you just want to install gcc you use 'yum' or 'rpm' to do that,
instead of compiling it yourself.
If you want to compile gcc, obviously you need a compiler of some kind.
It might seem weird but it's not, it's quite normal.
http://en.wikipedia.org/wiki/Bootstrapping_%28compilers%29
--
Syed Ahsan Ali Bokhari
Electronic Engineer
Research & Development Division
Pakistan Meteorological Department H-8/2, Islamabad.
Phone # off +92519250361
Cell # +923155145014
Fax # +92519250368
www.pmd.gov.pk
