public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Anthony Lee <al012@energex.com.au>
To: gcc-help@gcc.gnu.org
Subject: Re: Problem compiling gcc 2.95.2 on DEC Station 3000
Date: Sun, 17 Dec 2000 14:15:00 -0000	[thread overview]
Message-ID: <3A3D3A9B.8E407AFD@energex.com.au> (raw)
In-Reply-To: <Pine.A41.4.21.0012170937050.149628-100000@homer25.u.washington.edu>

Is there reason why you need the latest gcc? You might be able to
get an older version working? In addition, I believe that 
DEC used to supply another CD of associated products. You might find
a version of gcc on there that might work with Ultrix 4.3 but I think
it might too old.

Bryant Fujimoto wrote:
> 
> Hello,
>   I am trying to compile gcc-core-2.95.2 on a DEC Station 3000
> running ULTRIX V4.3 (Rev. 44)
> 
> after ./configure, I do 'make bootstrap-lean' and I get the
> following error message (I also include the command which
> produced the error).
> 
> stage1/xgcc -Bstage1/ -B/usr/local/mips-dec-ultrix4.3/bin/ -c  -DIN_GCC
> -O2 -g  -DHAVE_CONFIG_H    -I. -I. -I./config -I./../include cpplib.c
> cpplib.c: In function `do_assert':
> cpplib.c:2753: invalid operands to binary -
> cpplib.c: In function `do_unassert':
> cpplib.c:2829: invalid operands to binary -
> make[2]: *** [cpplib.o] Error 1
> make[2]: Leaving directory `/usr/users/library/gcc-2.95.2/gcc'
> make[1]: *** [bootstrap-lean] Error 1
> make[1]: Leaving directory `/usr/users/library/gcc-2.95.2/gcc'
> make: *** [bootstrap-lean] Error 1
> 
> I realize that the DEC station is a rather old computer, but does
> anyone have any idea what is causing this problem, and how to fix it?
> 
> Thanks,
> Bryant Fujimoto
> fujimoto@u.washington.edu

-- 
Anthony Lee	
Energex                                            
150 Charlotte Street                   ..--  __o 
Brisbane                          ....--   _ \<,_               
Qld 4000                         ____     (_)/
(_)                         
Australia
voice:+61 7 3407 4541
fax:  +61 7 3407 4607
email: AL012@energex.com.au


-----------------------------------------------------------------------------------------------------------------------------------------------------
This email message (and any accompanying file attachments) may contain confidential or 
privileged information and is intended for the sole use of the addressee named above. If you 
are not the intended recipient, or the person responsible for delivering this message to the 
intended recipient, please notify ENERGEX immediately and destroy any copies of the original 
message.

Any unauthorised review, use, alteration, disclosure or distribution of this email (including any 
attachments) by an unintended recipient is prohibited.

ENERGEX accepts no responsibility for the content of any email which is sent by an employee 
which is of a personal nature.

      reply	other threads:[~2000-12-17 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-17  9:44 Bryant Fujimoto
2000-12-17 14:15 ` Anthony Lee [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=3A3D3A9B.8E407AFD@energex.com.au \
    --to=al012@energex.com.au \
    --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).