From: Jeff Law <jeffreyalaw@gmail.com>
To: Mark Butt <mark@markwbutt.com>, Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
Date: Sun, 22 Jan 2023 11:40:46 -0700 [thread overview]
Message-ID: <0a2e72ff-e0ce-f413-aeeb-1bdb1cfbd512@gmail.com> (raw)
In-Reply-To: <1069636641.353816.1674409053357.JavaMail.zimbra@markwbutt.com>
On 1/22/23 10:37, Mark Butt wrote:
>
> No, there is no reason to be at 8.3.0 other than this was the minimum required. I thought that I might have better luck getting 8.3 to work vs
> a newer version given the age of the hardware, I will, however, try a newer version as suggested.
>
> Would you recommend going with a particular version or just get the latest and greatest?
I'd just go with the latest release. You could go with one of the
weekly development snapshots, but that may introduce problems you don't
want to deal with.
FWIW, I do 3-stage bootstraps of the alpha port in my tester once a week
(using qemu). This includes binutils, gcc, glibc and a kernel build
using the tip-of-trunk sources for each component. It's also a linux
environment, not a BSD environment.
While that work isn't directly applicable to you, it does provide some
degree of reassurance that the alpha port basically works. Any notable
issues are likely BSD specific.
http://law-sandy.freeddns.org:8080/job/alpha-linux-gnu/
jeff
next prev parent reply other threads:[~2023-01-22 18:40 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 [this message]
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
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=0a2e72ff-e0ce-f413-aeeb-1bdb1cfbd512@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=mark@markwbutt.com \
/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).