This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: installing gcc on a pc running Redhat Linux6.2


Michael Fothergill wrote:
> 
> I ran the config.guess and the output was
> 
> i686-pc-linux-gnu.
> 
> What does this mean.
> 

It means that you are running on a 686 machine that is running some form
of linux.


> When I ran install the machine did a few things and seemed to run out of
> steam
> 
> The end of the installation went as follows:
>
> cp: cannot create regular file `/usr/local/bin/#inst.21741#': Permission
> denied
> chmod: /usr/local/bin/g++: No such file or directory
> ln: /usr/local/bin/g++: No such file or directory
> cp: cannot create regular file `/usr/local/bin/#inst.21775#': Permission
> denied
> chmod: /usr/local/bin/c++filt: No such file or directory
> make[1]: [c++.install-common] Error 1 (ignored)
> case "c proto gcov CHILL c++ f77 java objc" in \
>   *[fF]77*) touch /usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/lang-f77;;
> \
>   *) rm -f /usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/lang-f77;; \
> esac
> touch: /usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/lang-f77: No such
> file or directory
> make[1]: *** [f77.install-common] Error 1
> make[1]: Leaving directory `/home/gcc/gcc-2.95.2/cccexec/gcc'
> make: *** [install-gcc] Error 2
> [mikef@redhat cccexec]$
> [mikef@redhat cccexec]$
> 
> Do you think GCC installed correctly?  The configure and the build seemed to
> work OK.
>

Definitely not.

You do not have write permission into /usr/local.  You need to do the
final install as root unless you specify a prefix where you can write.
 
> How do I actually run the compiler (e.g. the Fortran compiler)
> Whereabout in the documentation are the instructions?
>

Put the compiler in your path.  Run it :)  The documentation covers the
options available.  A simple command line would be:

gcc hello.c -o hello

and will produce an output (-o) executable called hello from the input
(c) file hello.c.
 
> 
> How do I test it?
> 

make check-gcc in the build directory.  But I think you just want to
make sure that it will work, in that case just compile something as
above.

-eric

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]