public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: BSD Bob <bsdbob@weedcon1.cropsci.ncsu.edu>
To: help-gcc@gnu.org
Subject: Need OLD GCC 2.5.8 or 2.7.xx for Solaris 1 -- where?
Date: Tue, 07 Dec 1999 16:20:00 -0000	[thread overview]
Message-ID: <82jbqj$2sj$1@uni00nw.unity.ncsu.edu> (raw)

I have an aging SparcBook 2 running Solaris 1.0.1 that is unupgradable.
It has an old user contrib port of gcc-2.1 on its Solaris CD, but, when
that port is installed, it generates internal compiler errors when
compiling anything serious (like gcc 2.5.8 or 2.7.2.3).  I really would
like to get a working gcc port up on it.  All I need is 2.5.8, but
anything that works, will also do.  My goal is to compile TeX, groff,
and a working gcc and a few gnu tools, so I can  run Apache on the
beast as a portable web server.

1.)  Anyone know of the whereabouts of any SparcBook 2 ports of any vintage
     of gcc?

2.)  Anyone know of the whereabouts of any pre-2.5.8 gcc sources so that
     I might try recompiling an early port and then work that up to a
     later port?

3).  Anyone know, for sure, if the native SunOS compiler of a SparcBook 2
     Solaris will properly compile a working gcc?  If so, which version
     of gcc (the machine is only a tiny laptop with a pair of 300mb hd's
     so it can't attack easily the full 2.95.2 kind of thing).

Any suggestions, insights, horror stories, etc., are appreciated.

Thanks

Bob

WARNING: multiple messages have this Message-ID
From: BSD Bob <bsdbob@weedcon1.cropsci.ncsu.edu>
To: help-gcc@gnu.org
Subject: Need OLD GCC 2.5.8 or 2.7.xx for Solaris 1 -- where?
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <82jbqj$2sj$1@uni00nw.unity.ncsu.edu> (raw)
Message-ID: <19991231222400.g1SGQSuLmUaApUkdb51P0REG-zhFay9VQd9l0SyIlR0@z> (raw)

I have an aging SparcBook 2 running Solaris 1.0.1 that is unupgradable.
It has an old user contrib port of gcc-2.1 on its Solaris CD, but, when
that port is installed, it generates internal compiler errors when
compiling anything serious (like gcc 2.5.8 or 2.7.2.3).  I really would
like to get a working gcc port up on it.  All I need is 2.5.8, but
anything that works, will also do.  My goal is to compile TeX, groff,
and a working gcc and a few gnu tools, so I can  run Apache on the
beast as a portable web server.

1.)  Anyone know of the whereabouts of any SparcBook 2 ports of any vintage
     of gcc?

2.)  Anyone know of the whereabouts of any pre-2.5.8 gcc sources so that
     I might try recompiling an early port and then work that up to a
     later port?

3).  Anyone know, for sure, if the native SunOS compiler of a SparcBook 2
     Solaris will properly compile a working gcc?  If so, which version
     of gcc (the machine is only a tiny laptop with a pair of 300mb hd's
     so it can't attack easily the full 2.95.2 kind of thing).

Any suggestions, insights, horror stories, etc., are appreciated.

Thanks

Bob

             reply	other threads:[~1999-12-07 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-07 16:20 BSD Bob [this message]
1999-12-31 22:24 ` BSD Bob

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='82jbqj$2sj$1@uni00nw.unity.ncsu.edu' \
    --to=bsdbob@weedcon1.cropsci.ncsu.edu \
    --cc=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).