public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fsrahman at bu dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/104628] New: Error when bootstrapping CMake: Problem while running make
Date: Tue, 22 Feb 2022 04:20:55 +0000 [thread overview]
Message-ID: <bug-104628-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104628
Bug ID: 104628
Summary: Error when bootstrapping CMake: Problem while running
make
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: fsrahman at bu dot edu
Target Milestone: ---
Created attachment 52486
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52486&action=edit
section from cmake_bootstrap.log
gcc version:
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Please see error log below after bootstrapping and running make command for
CMake in terminal:
/tmp/cmake-3.22.2/Source/cmAlgorithms.h:61:43: required from here
/usr/include/c++/9/ext/new_allocator.h:173:2: internal compiler error:
Segmentation fault
173 | operator!=(const new_allocator&, const new_allocator<_Up>&)
| ^~~~~~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-9/README.Bugs> for instructions.
make: *** [Makefile:154: cmFindProgramCommand.o] Error 1
---------------------------------------------
Error when bootstrapping CMake:
Problem while running make
---------------------------------------------
Log of errors: /tmp/cmake-3.22.2/Bootstrap.cmk/cmake_bootstrap.log
next reply other threads:[~2022-02-22 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 4:20 fsrahman at bu dot edu [this message]
2022-02-22 7:34 ` [Bug bootstrap/104628] " pinskia at gcc dot gnu.org
2024-04-13 1:12 ` [Bug middle-end/104628] " pinskia 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-104628-4@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).