public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@aarsen.me>
To: Mark Butt <mark@markwbutt.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	Jeff Law <jeffreyalaw@gmail.com>,
	Jonathan Wakely <jwakely.gcc@gmail.com>,
	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:25:24 +0100	[thread overview]
Message-ID: <861qnflqrz.fsf@aarsen.me> (raw)
In-Reply-To: <1181772750.416994.1674847272046.JavaMail.zimbra@markwbutt.com>

[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]

Hi Mark,

Mark Butt <mark@markwbutt.com> writes:

> Thanks Segher!
> I tried 12.2 a few days ago but I am getting errors that I think are about the
> compiler that comes with OpenBSD being too old to build 12.2.
> I haven't given up yet, but I think I need to reinstall OpenBSD for sanity sake
> to make sure I haven't messed something up over the weeks of trying to figure
> it out.

OpenBSD 7.2 seems to includes GCC 4.2.1 and Clang 13.  The former is too
old, however, the latter should work fine.  Try to configure with
CC=clang CXX=clang++ or something like that.

> This morning I found a great article about how to build gcc for an Alpha
> emulated VM running Tru64.  I am going to try to roughly translate what I can
> in to OpenBSD to see if that helps.
> I do have Tru64 on another set of SCSI disks so I might give it a go... just to
> see if the steps work for a stock Tru64 5.1b.
>
> When I started this small project I didn't think it would much trouble at all.
> I had assumed modern OpenBSD would be similar to using something like modern
> AIX which supports a lot of GNU-linked products very well... either that was a
> poor assumption on my part, I am doing something wrong, the Alpha architecture
> (yes, ancient I know) or a combination of several of those.
>
> When I do have a working GCC installation I will report back with the steps
> required to get there.  Incase anyone else happens to feel the need to compile
> GCC on an old Alpha.
> I am thinking I am getting close...  GCC is building it seems, but encounters
> errors during the subsequent steps.  It complains that it cannot create
> executables.
>
> I did notice that the configure script is detecting the host as:  alpha-unknown-openbsd7.2
> Does anyone know if that looks right or if I should be manually specifying the host type?

Assuming this is an Alpha host, that seems right.

> Again, thanks all for the help and taking the time to respond.
> -M

Have a nice night.
-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]

  reply	other threads:[~2023-01-27 19:30 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ć [this message]
2023-01-27 20:17           ` Jonathan Wakely
2023-01-27 21:14           ` Segher Boessenkool
2023-01-27 19:41 ` Christer Solskogen

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=861qnflqrz.fsf@aarsen.me \
    --to=arsen@aarsen.me \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=mark@markwbutt.com \
    --cc=segher@kernel.crashing.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).