From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Mark Butt <mark@markwbutt.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
Jeff Law <jeffreyalaw@gmail.com>,
gcc-help <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:17:31 +0000 [thread overview]
Message-ID: <CAH6eHdQAooYkARvbXz6m3QOy9tRQ110B7jA3PRBEdjuyuuuzsg@mail.gmail.com> (raw)
In-Reply-To: <1181772750.416994.1674847272046.JavaMail.zimbra@markwbutt.com>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
On Fri, 27 Jan 2023, 19:21 Mark Butt, <mark@markwbutt.com> wrote:
>
> 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.
>
AIX has people actively testing GCC regularly, and reporting bugs and
contributing patches. Nobody does that for openbsd so it's unsurprising
that it bitrots, especially for the combination of alpha and openbsd which
will be even less frequently tested.
next prev parent reply other threads:[~2023-01-27 20:17 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 [this message]
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=CAH6eHdQAooYkARvbXz6m3QOy9tRQ110B7jA3PRBEdjuyuuuzsg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jeffreyalaw@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).