public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dennis Clarke <dclarke@blastwave.org>
To: gcc-help@gcc.gnu.org
Subject: Re: archeology : Compiling gcc-3.4.6 on sparc sun4m Solaris 2.5.1
Date: Sun, 17 Jul 2022 19:34:57 -0400	[thread overview]
Message-ID: <25261203-4be1-1fd8-1121-c787b90110ea@blastwave.org> (raw)
In-Reply-To: <70c00fbd-bb21-f790-8ef7-dedb53b31d7e@blastwave.org>

On 7/16/22 22:59, Dennis Clarke via Gcc-help wrote:
> 
> I simply had to give this a try and maybe even be able to bootstrap gcc
> on this old old hardware. Just for fun and because I saw someone else
> trying gcc 3.4.6 on a Solaris 9 server.
> 
> So firstly, yes, this is very real hardware but of course the old
> battery in the SPARCStation 20 prom gave up long ago. So I made the
> machine reasonably sane as 08:00:20:c0:ff:ee :)
> 

Sorted it out just fine :

ganymede$
ganymede$ uname -a
SunOS ganymede 5.5.1 Generic_103640-12 sun4m sparc SUNW,SPARCstation-20
ganymede$ /opt/imed/gcc/gcc346/bin/gcc --version
gcc (GCC) 3.4.6
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

ganymede$


That may be able to bootstrap a ver 5.x but I am not so sure when
Solaris 2.5.1 was dropped entirely. Should be interesting to see.



-- 
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional

      reply	other threads:[~2022-07-17 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17  2:59 Dennis Clarke
2022-07-17 23:34 ` Dennis Clarke [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=25261203-4be1-1fd8-1121-c787b90110ea@blastwave.org \
    --to=dclarke@blastwave.org \
    --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).