public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Christopher <echristo@cygnus.com>
To: Michael Fothergill <mikef20000@hotmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: installing gcc on a pc running Redhat Linux6.2
Date: Fri, 15 Sep 2000 17:32:00 -0000	[thread overview]
Message-ID: <39C2C1D1.AB52F521@cygnus.com> (raw)
In-Reply-To: <F315QUUBPcZi71mrvoG0000e3cd@hotmail.com>

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

      reply	other threads:[~2000-09-15 17:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-15 17:25 Michael Fothergill
2000-09-15 17:32 ` Eric Christopher [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39C2C1D1.AB52F521@cygnus.com \
    --to=echristo@cygnus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mikef20000@hotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).