public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tanes Sriviroolchai <tanes73@yahoo.com>
To: Brother Tuck <brothertuck72@hotmail.com>,
	Joe Buck <jbuck@racerx.synopsys.com>,
	gcc@gcc.gnu.org, gcc-help@gcc.gnu.org
Subject: Unable to compile gcc 2.95.3 on NCR 4.0
Date: Tue, 03 Apr 2001 19:35:00 -0000	[thread overview]
Message-ID: <20010404023547.69211.qmail@web11101.mail.yahoo.com> (raw)

>I'm just trying to compile gcc 2.95.3 on i586-ncr-sysv4.3.03.
>Compiling the gcc using an old gcc 2.7.2.x I get a coredump when the
>file 
>gencheck is launched. This segmentation fault occured only if the tools

>gencheck is compiled using stage1
>If someone have found the same problem on NCR or another system, please
tell 
>what's wrong and howto correct this problem safely.

I've sucessfully compiled 2.95.2 (and use it since it was released) and
2.95.3 without any problems without any changes a bit from source. First
I build binutils the newest version (mine is 2.10) using stock compiler
(NCR High Performance C Compiler 3.0 - package scde) and gnu make
3.79.1. Then, I build gcc 2.7.2.x. After that I make bootstrap gcc
2.95.2. Then you can use gcc 2.95.2 to make bootstrap gcc 2.95.3.

Regards,
Tanes Sriviroolchai
NCR (Thailand) Ltd.
 

__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/

             reply	other threads:[~2001-04-03 19:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-03 19:35 Tanes Sriviroolchai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-04  5:39 Brother Tuck
2001-04-02  4:47 Brother Tuck
2001-04-02 12:07 ` Joe Buck
2001-04-02 14:53   ` Emmanuel Soden
2001-04-02 14:56     ` Joe Buck

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=20010404023547.69211.qmail@web11101.mail.yahoo.com \
    --to=tanes73@yahoo.com \
    --cc=brothertuck72@hotmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@racerx.synopsys.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).