gcc44 installs correctly but default gcc is still used

[Josie Reinhardt]

Thanks for your reply,

$ which gcc
/usr/bin/gcc

$ echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/sw/bin/:/sw/sbin/:/usr/local/bin/:/usr/local/sbin/:/bin/:/sbin:/usr/bin/:/usr/sbin/:/opt/local/bin/:/opt/local/sbin:/usr/local/mysql/bin/:/sw/bin/:(various
application specific paths)

$ ls -l /opt/local/bin/gcc/
-rwxr-xr-x  3 root  admin  342200 Apr 17 00:32 /opt/local/bin/gcc/

Josie


On Wed, May 23, 2012 at 4:25 PM, Frank Schima
<macsforever2000 at macports.org> wrote:
>
> On May 23, 2012, at 2:08 PM, Josie Reinhardt wrote:
>
>> This is probably a very unix newby question so I'm sorry to ask it, but I
>> can't find a good solution in the current tickets, guide or via
>> googling...
>>
>> I followed this guide (http://jswails.wikidot.com/mac-os-x) to install
>> macports, and use it to update to v 4.4 of the gcc compiler.  Note that I
>> am not doing this for the purpose of using the program that the guide-
>> maker is trying to install (amber).  I need gcc4.4 for another reason
>> entirely.
>>
>> Everything appears to be installed properly based on the output when I run
>> "install" and "select" again.  However, when I run gcc, it's clear that
>> gcc 4.2 (the default for me) is still being used  (see below).
>>
>> How do I get my computer to actually use the ported version (gcc4.4)?
>>
>> --------------------------------
>>
>> $ sudo port install gcc44 gcc_select
>> Password:
>> --->  Computing dependencies for gcc44
>> --->  Cleaning gcc44
>> --->  Cleaning gcc_select
>> --->  Scanning binaries for linking errors: 100.0%
>> --->  No broken files found.
>> $ sudo port select gcc mp-gcc44
>> Selecting 'mp-gcc44' for 'gcc' succeeded. 'mp-gcc44' is now active.
>> $ gcc
>> i686-apple-darwin10-gcc-4.2.1: no input files
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
>
> Did you try in a new Terminal window?
>
> Looks like you have a path problem. What is the output of the following 3 statements - one at a time?
>
> which gcc
> echo $PATH
> ls -l /opt/local/bin/gcc
>
>
> Cheers!
> Frank
>