Konstantinos Bekiaris wrote:
> 
> 
> On Tue, Feb 9, 2010 at 8:53 PM, walt <w41...@gmail.com
> <mailto:w41...@gmail.com>> wrote:
> 
>     On 02/08/2010 10:27 PM, Konstantinos Bekiaris wrote:
> 
>            What do you have in /etc/env.d/gcc/?  I have this:
> 
>            #ls -l /etc/env.d/gcc/
>            total 16
>            -rw-r--r-- 1 root root  32 2010-02-08 11:53
>         config-i686-pc-linux-gnu
>            -rw-r--r-- 1 root root 235 2009-01-29 12:33
>         i686-pc-linux-gnu-4.1.2
>            -rw-r--r-- 1 root root 235 2009-07-04 09:02
>         i686-pc-linux-gnu-4.3.2
>            -rw-r--r-- 1 root root 235 2010-01-10 12:29
>         i686-pc-linux-gnu-4.3.4
> 
>            Do you still have any version of gcc installed?
> 
>         drwxr-xr-x 2 root root 4096 Jan 24 13:16 .
>         drwxr-xr-x 5 root root 4096 Jan 24 13:17 ..
>         lrwxrwxrwx 1 root root   25 Jan 24 06:25 .NATIVE ->
>         x86_64-pc-linux-gnu-4.1.2
>         -rw-r--r-- 1 root root   34 Jan 24 06:25 config-x86_64-pc-linux-gnu
>         -rw-r--r-- 1 root root  381 Jan 24 06:25 x86_64-pc-linux-gnu-4.3.4
> 
> 
>     There's one problem.  .NATIVE is pointing at a non-existent file.
>      Assuming
>     your machine really does have gcc-4.3.4, .NATIVE should be pointing at
>     x86_64-pc-linux-gnu-4.3.4, and the contents of
>     config-x86_64-pc-linux-gnu
>     should be:   CURRENT=x86_64-pc-linux-gnu-4.3.4
> 
>     I don't know why there are two different ways to point at the same
>     gcc, but
>     that's the way gcc-config does it.
> 
>     Correct those two files and see if it helps.
> 
> 
>         I think that i have gcc, the problem is that it is not correctly
>         linked
> 
>     > with tha appropriate files-libraries.
> 
>     You can run /usr/x86_64-pc-linux-gnu/gcc-bin/4.3.4/gcc directly to
>     see if
>     it works.
> 
> 
>     It works, when i am in the folder
>     /usr/x86_64-pc-linux-gnu/gcc-bin/4.3.4/ and i tried ./gcc, it works.
>     Can you please show me the way  i must put the links in order to
>     work from anywhere(sym links or hard links)? I think it is ln -s
>     //usr/x86_64-pc-linux-gnu/gcc-bin/4.3.4/gcc " folder".

This is weird.  I have a small binary /usr/bin/gcc which is obviously just
a stub for starting the version of gcc you select with gcc-config.  The
weird part is that no package claims that file so I don't know how it got
there but the date suggests it was put there by gcc-4.3.4.

$ls -l /usr/bin/gcc*
-rwxr-xr-x 1 root root  9572 2010-01-10 12:29 /usr/bin/gcc   <******* this one
lrwxrwxrwx 1 root root    58 2009-01-29 12:34 /usr/bin/gcc-4.1.2 -> 
/usr/i686-pc-linux-gnu/gcc-bin/4.1.2/i686-pc-linux-gnu-gcc
lrwxrwxrwx 1 root root    58 2009-07-04 09:03 /usr/bin/gcc-4.3.2 -> 
/usr/i686-pc-linux-gnu/gcc-bin/4.3.2/i686-pc-linux-gnu-gcc
lrwxrwxrwx 1 root root    58 2010-01-10 12:29 /usr/bin/gcc-4.3.4 -> 
/usr/i686-pc-linux-gnu/gcc-bin/4.3.4/i686-pc-linux-gnu-gcc
-rwxr-xr-x 1 root root 21711 2010-02-13 14:33 /usr/bin/gcc-config

Do you have a similar /usr/bin/gcc?  It seems to run whatever file
/etc/env.d/gcc/.NATIVE is pointing to, so that symlink must be right for
/usr/bin/gcc to work properly.


Reply via email to