From: Segher Boessenkool <segher@kernel.crashing.org>
To: Mark Butt <mark@markwbutt.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
Jonathan Wakely <jwakely.gcc@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 15:14:11 -0600 [thread overview]
Message-ID: <20230127211411.GU25951@gate.crashing.org> (raw)
In-Reply-To: <1181772750.416994.1674847272046.JavaMail.zimbra@markwbutt.com>
On Fri, Jan 27, 2023 at 03:51:12PM -0330, Mark Butt wrote:
> 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.
A C++11 compiler is required:
ISO C++11 compiler
Necessary to bootstrap GCC. GCC 4.8.3 or newer has sufficient
support for used C++11 features, with earlier GCC versions you
might run into implementation bugs.
> 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?
That isn't the host. The target triple is cpu-vendor-os. "unknown"
is pretty normal here, and doesn't usually make a difference. If you
do use something here you will have to use the same thing for all tools,
so it is easier to just use the detected thing usually.
Segher
next prev parent reply other threads:[~2023-01-27 21:15 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 [this message]
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=20230127211411.GU25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-help@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--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).