public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104134] Bootstrap on FreeBSD files compiling gcc/cp/error.cc
Date: Thu, 20 Jan 2022 05:53:58 +0000 [thread overview]
Message-ID: <bug-104134-4-cGHPUd8RBj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104134-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104134
--- Comment #14 from kargl at gcc dot gnu.org ---
(In reply to Rimvydas (RJ) from comment #13)
> Error is triggered on Linux (LFS-next testing) builds too, but only when
> configured as:
> ../configure --enable-bootstrap --disable-nls --disable-multilib
>
Removing --disable-nls from my configure command line allows bootstrap to
succeed on FreeBSD.
next prev parent reply other threads:[~2022-01-20 5:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 22:32 [Bug bootstrap/104134] New: " kargl at gcc dot gnu.org
2022-01-19 22:33 ` [Bug bootstrap/104134] " kargl at gcc dot gnu.org
2022-01-19 22:41 ` kargl at gcc dot gnu.org
2022-01-19 22:48 ` [Bug c++/104134] " pinskia at gcc dot gnu.org
2022-01-19 23:16 ` msebor at gcc dot gnu.org
2022-01-19 23:36 ` kargl at gcc dot gnu.org
2022-01-19 23:54 ` jakub at gcc dot gnu.org
2022-01-19 23:57 ` jakub at gcc dot gnu.org
2022-01-20 0:13 ` sgk at troutmask dot apl.washington.edu
2022-01-20 0:17 ` kargl at gcc dot gnu.org
2022-01-20 0:24 ` kargl at gcc dot gnu.org
2022-01-20 0:25 ` msebor at gcc dot gnu.org
2022-01-20 0:29 ` sgk at troutmask dot apl.washington.edu
2022-01-20 0:30 ` jakub at gcc dot gnu.org
2022-01-20 1:55 ` sgk at troutmask dot apl.washington.edu
2022-01-20 4:15 ` rimvydas.jas at gmail dot com
2022-01-20 5:53 ` kargl at gcc dot gnu.org [this message]
2022-01-20 8:37 ` [Bug c++/104134] Bootstrap with --disable-nls " marxin at gcc dot gnu.org
2022-01-20 11:03 ` cvs-commit at gcc dot gnu.org
2022-01-20 11:04 ` marxin at gcc dot gnu.org
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=bug-104134-4-cGHPUd8RBj@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).