From: Christer Solskogen <christer.solskogen@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
Date: Fri, 27 Jan 2023 20:41:39 +0100 [thread overview]
Message-ID: <tr19dj$2rl$1@ciao.gmane.io> (raw)
In-Reply-To: <B49004E0-0B3D-4AFF-BEF1-CDDC2FDAC559@markwbutt.com>
On 20.01.2023 16:40, Mark Butt wrote:
> Hi Everyone,
>
> I have OpenBSD 7.2 installed and running on an AlphaServer 4100. DEC Alpha EV5 processors.
> No major issues with getting it running on this old hardware other than a slight bug one of the developers over at OpenBSD squashed for me.
>
> I have been having great success with building modern tools and software on the system. No problems at all. Except for one…
>
> A particular piece of software I am trying to build requires GCC 8.3.0 which is much newer than the version that comes with OpenBSD. I am attempting to build and install GCC 8.3.0 in a separate location from the main system compiler as OpenBSD doesn’t usually take kindly to having its system compiler version changed.
>
IIRC OpenBSD doesn't have any prebuilt packages for alpha, but you
should be able to install gcc by using ports, which does most of the
heavy lifting for you. In case your application *really* needs 8.x, the
ports system have that too.
--
chs
prev parent reply other threads:[~2023-01-27 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 15:40 Mark Butt
2023-01-20 17:30 ` Jonathan Wakely
2023-01-22 17:37 ` Mark Butt
2023-01-22 18:36 ` Jonathan Wakely
2023-01-22 18:40 ` Jeff Law
2023-01-27 17:58 ` Segher Boessenkool
2023-01-27 19:21 ` Mark Butt
2023-01-27 19:25 ` Arsen Arsenović
2023-01-27 20:17 ` Jonathan Wakely
2023-01-27 21:14 ` Segher Boessenkool
2023-01-27 19:41 ` Christer Solskogen [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='tr19dj$2rl$1@ciao.gmane.io' \
--to=christer.solskogen@gmail.com \
--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).