public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sajarvis at bu dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/63509] New: Misleading error message when building gcc without C++ compiler installed Date: Sat, 11 Oct 2014 01:05:00 -0000 [thread overview] Message-ID: <bug-63509-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63509 Bug ID: 63509 Summary: Misleading error message when building gcc without C++ compiler installed Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: sajarvis at bu dot edu Created attachment 33685 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33685&action=edit Full output during make. When building gcc with no C++ compiler installed, configuration succeeds, then make fails with error message: configure: error: error verifying int64_t uses long long Steps to cause: 1) Don't install a C++ compiler 2) $ ./configure --prefix=$HOME/dev/gcc/bld --enable-multilib 3) $ make I think the error should be more specific to the issue (no C++ compiler found) and probably caught earlier. System: Fedora 20, Linux 3.16 building gcc trunk, version r216105 More of the log (full log attached): [...] checking for int16_t... yes checking for int32_t... yes checking for int64_t... yes checking for long long int... yes checking for intmax_t... yes checking for intptr_t... yes checking for uint8_t... yes checking for uint16_t... yes checking for uint32_t... yes checking for uint64_t... yes checking for unsigned long long int... yes checking for uintmax_t... yes checking for uintptr_t... yes checking for int64_t underlying type... long long configure: error: error verifying int64_t uses long long make[2]: *** [configure-stage1-gcc] Error 1 make[2]: Leaving directory `/home/sjarvis/dev/gcc/srcdir' make[1]: *** [stage1-bubble] Error 2 make[1]: Leaving directory `/home/sjarvis/dev/gcc/srcdir' make: *** [all] Error 2
next reply other threads:[~2014-10-11 1:05 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-11 1:05 sajarvis at bu dot edu [this message] 2014-10-12 20:02 ` [Bug other/63509] " manu at gcc dot gnu.org 2015-01-09 17:54 ` rpsene at linux dot vnet.ibm.com 2015-02-26 13:29 ` rjones at redhat dot com 2015-05-29 18:25 ` paul at greenberg dot pro 2015-10-18 20:34 ` tzachinoy at gmail dot com
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-63509-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: linkBe 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).