public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: jerry@cs.ucsb.edu, oliva@dcc.unicamp.br
Cc: egcs@egcs.cygnus.com
Subject: Re: bootstrapping with `cc -n32' on IRIX 6.3 fails compare
Date: Wed, 24 Mar 1999 05:13:00 -0000	[thread overview]
Message-ID: <199903241313.IAA19571@caip.rutgers.edu> (raw)

 > From: Alexandre Oliva <oliva@dcc.unicamp.br>
 >  
 > On Mar 24, 1999, jerry@cs.ucsb.edu (Jerry James) wrote:
 >  
 > > On Mar 24, 1999, you wrote:
 > >> On Mar 23, 1999, "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> wrote:
 >  
 > > [snip]
 >  
 > >> > I don't know if the version of the compiler is tied to the OS or not. 
 > >> > What version of the compiler are you using?
 > >> 
 > >> Dunno, how can I find it out?  I tried various command-line flags and
 > >> nothing helped.  I even looked at the manual! :-D
 >  
 > > Use the "versions" command.
 >  
 > Thanks.  I get:
 >  
 > oliva@duerer% versions | grep c_dev
 > I  c_dev                11/12/97  C, 7.0
 >  
 > Pretty old, huh? :-(

	PS: I think I recall Jim W. specifically mentioning that some
versions of 7.0 had bugs which caused cc -n32 to fail bootstrapping gcc. 
This came up in our discussion about the o32/n32 libiberty problem but
you'd have to ask him or search the archives back through last November
to get details. 

		--Kaveh
--
Kaveh R. Ghazi			Engagement Manager / Project Services
ghazi@caip.rutgers.edu		Qwest Internet Solutions

WARNING: multiple messages have this Message-ID
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: jerry@cs.ucsb.edu, oliva@dcc.unicamp.br
Cc: egcs@egcs.cygnus.com
Subject: Re: bootstrapping with `cc -n32' on IRIX 6.3 fails compare
Date: Wed, 31 Mar 1999 23:46:00 -0000	[thread overview]
Message-ID: <199903241313.IAA19571@caip.rutgers.edu> (raw)
Message-ID: <19990331234600.xCPmET7Uy1zEZr1w3aWKeFc2jhPlNh_hfsNVqXkyP6o@z> (raw)

 > From: Alexandre Oliva <oliva@dcc.unicamp.br>
 >  
 > On Mar 24, 1999, jerry@cs.ucsb.edu (Jerry James) wrote:
 >  
 > > On Mar 24, 1999, you wrote:
 > >> On Mar 23, 1999, "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> wrote:
 >  
 > > [snip]
 >  
 > >> > I don't know if the version of the compiler is tied to the OS or not. 
 > >> > What version of the compiler are you using?
 > >> 
 > >> Dunno, how can I find it out?  I tried various command-line flags and
 > >> nothing helped.  I even looked at the manual! :-D
 >  
 > > Use the "versions" command.
 >  
 > Thanks.  I get:
 >  
 > oliva@duerer% versions | grep c_dev
 > I  c_dev                11/12/97  C, 7.0
 >  
 > Pretty old, huh? :-(

	PS: I think I recall Jim W. specifically mentioning that some
versions of 7.0 had bugs which caused cc -n32 to fail bootstrapping gcc. 
This came up in our discussion about the o32/n32 libiberty problem but
you'd have to ask him or search the archives back through last November
to get details. 

		--Kaveh
--
Kaveh R. Ghazi			Engagement Manager / Project Services
ghazi@caip.rutgers.edu		Qwest Internet Solutions

             reply	other threads:[~1999-03-24  5:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-24  5:13 Kaveh R. Ghazi [this message]
1999-03-24  5:20 ` Alexandre Oliva
1999-03-31 23:46   ` Alexandre Oliva
1999-03-31 23:46 ` Kaveh R. Ghazi
  -- strict thread matches above, loose matches on Subject: below --
1999-03-24  6:16 N8TM
1999-03-31 23:46 ` N8TM
1999-03-24  5:10 Kaveh R. Ghazi
1999-03-31 23:46 ` Kaveh R. Ghazi
1999-03-23  9:35 Kaveh R. Ghazi
1999-03-24  0:04 ` Alexandre Oliva
     [not found]   ` <tprvhfruwva.fsf@cs.ucsb.edu>
1999-03-24  0:32     ` Alexandre Oliva
     [not found]       ` <tprsoavuvw0.fsf@cs.ucsb.edu>
1999-03-24  0:45         ` Alexandre Oliva
1999-03-31 23:46           ` Alexandre Oliva
1999-03-31 23:46       ` Alexandre Oliva
1999-03-31 23:46   ` Alexandre Oliva
     [not found] ` <oriubr70o5.fsf.cygnus.egcs@dcc.unicamp.br>
1999-03-24 12:41   ` Jim Wilson
1999-03-31 23:46     ` Jim Wilson
1999-03-31 23:46 ` Kaveh R. Ghazi
1999-03-21 10:01 Alexandre Oliva
1999-03-31 23:46 ` Alexandre Oliva

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=199903241313.IAA19571@caip.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --cc=egcs@egcs.cygnus.com \
    --cc=jerry@cs.ucsb.edu \
    --cc=oliva@dcc.unicamp.br \
    /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).