public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "youfan.noey at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/66508] New: Attempt to Compile gcc-6.0 on OSX 10.9.4 cause segmentation fault Date: Thu, 11 Jun 2015 12:50:00 -0000 [thread overview] Message-ID: <bug-66508-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66508 Bug ID: 66508 Summary: Attempt to Compile gcc-6.0 on OSX 10.9.4 cause segmentation fault Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: youfan.noey at gmail dot com Target Milestone: --- Created attachment 35757 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35757&action=edit config.log file Compiler being used is: clang-600.0.56 Build with command line command: cd ~/src/build/gcc && rm -rf * ~/src/gcc/configure --prefix=$HOME/sandbox --enable-languages=c++ --enable-checking=release > /dev/null 2>/dev/null /usr/bin/time make -j11 bootstrap > out.log 2> err.log It cause segmentation fault when process configure:3462: /Users/jieyuandai/src/build/gcc/./gcc/xgcc -B/Users/jieyuandai/src/build/gcc/./gcc/ -B/usr/local/x86_64-apple-darwin13.3.0/bin/ -B/usr/local/x86_64-apple-darwin13.3.0/lib/ -isystem /usr/local/x86_64-apple-darwin13.3.0/include -isystem /usr/local/x86_64-apple-darwin13.3.0/sys-include -o conftest -g -O2 conftest.c >&5 <built-in>: internal compiler error: Segmentation fault: 11 libbacktrace could not find executable to open Please submit a full bug report, with preprocessed source if appropriate.
next reply other threads:[~2015-06-11 12:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-11 12:50 youfan.noey at gmail dot com [this message] 2015-06-12 8:55 ` [Bug bootstrap/66508] " redi at gcc dot gnu.org 2015-06-12 9:24 ` dominiq at lps dot ens.fr 2015-06-12 11:06 ` youfan.noey at gmail dot com 2015-06-13 11:39 ` iains at gcc dot gnu.org 2015-06-14 13:56 ` youfan.noey 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-66508-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).