public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Eric Gravel" <wildgod@hotmail.com>
To: gcc-help@gcc.gnu.org
Subject: Can't locate newly compiled 2.95.2 binaries!?
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <20000123185440.20294.qmail@hotmail.com> (raw)
Message-ID: <20000401000000.Z9fN5dGlnm9_ZkhziwwYD-dD3ufxBTkn7Gokuvg19xU@z> (raw)

Hi,

I've been trying to upgrade my c compiler, gcc version pgcc-2.91.66
19990314 (egcs-1.1.2 release), for the past day now and until this
morning I had no success.

Last time I tried compiling I was getting the following error:
"xgcc: Internal compiler error: program cc1 got fatal signal 11."
I manage to overcome this problem by compiling a new version
of make though I don't think this matter, binutils 2.9.1 and glibc
2.1.2 with the crypt & linuxthread add on.

Now when I compiled gcc 2.95.2 I used the following commands
./configure --prefix=/usr --exec-prefix=/usr
make bootstrap
make check
make install

Read the installation document, I should find my binaries in /usr/bin
right?  Looking at the content matching the date (Jan 23 in the wee
hours 3am) there's no gcc or anything that looks like a compiler
executable. The only thing close is called c++filt.  I doubt that is it.



So, does anyone else have a suggestion as to where I should be looking
or even better, what commands I should have used to compile and
install gcc 2.95.2?  Is there a log of what configure & make perform?


Thanks for the help,

    Eric A. Gravel


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

             reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-23 10:55 Eric Gravel [this message]
2000-01-23 23:13 ` llewelly
2000-04-01  0:00   ` llewelly
2000-04-01  0:00 ` Eric Gravel

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=20000123185440.20294.qmail@hotmail.com \
    --to=wildgod@hotmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /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).