public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nico at josuttis dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/54834] bootstrap fails when building libbacktrace Date: Thu, 01 Nov 2012 10:14:00 -0000 [thread overview] Message-ID: <bug-54834-4-zsE7lyGqsU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54834-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54834 Nicolai Josuttis <nico at josuttis dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nico at josuttis dot de --- Comment #7 from Nicolai Josuttis <nico at josuttis dot de> 2012-11-01 10:14:30 UTC --- I got the same problem when switching from revision 1191942 (Oct 1st, 2012) to revision 193061 (Nov 1st, 2012). The effect was that the following files existed in the build tree: -rw-r--r-- 1 nico None 10659 Sep 21 10:16 gcc/include/unwind.h lrwxrwxrwx 1 nico None 36 Oct 2 00:04 i686-pc-cygwin/libgcc/unwind.h -> ../../../src/libgcc/unwind-generic.h After removing gcc/include/unwind.h the problem disappeared. As you can see, my environment was: CygWin under Windows 7 x64 (i686-pc-cygwin) Config settings were: ../src/configure \ --enable-languages=c++ \ --disable-bootstrap \ --prefix=/cygdrive/p/gcc/gcc$VERSION \ --program-suffix=$VERSION \ --with-gxx-include-dir=/cygdrive/p/gcc/gcc$VERSION-include \ --disable-lto \ --disable-sjlj-exceptions \ 2>&1 | tee -a ../make.log
next prev parent reply other threads:[~2012-11-01 10:14 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-06 10:16 [Bug bootstrap/54834] New: " tobi at gcc dot gnu.org 2012-10-08 16:18 ` [Bug bootstrap/54834] " ian at airs dot com 2012-10-08 16:19 ` ian at airs dot com 2012-10-09 14:01 ` tobi at gcc dot gnu.org 2012-10-09 14:06 ` tobi at gcc dot gnu.org 2012-10-10 7:45 ` tobi at gcc dot gnu.org 2012-10-13 10:42 ` tobi at gcc dot gnu.org 2012-11-01 10:14 ` nico at josuttis dot de [this message] 2013-01-01 16:23 ` ian at gcc dot gnu.org 2013-01-01 16:24 ` ian at airs 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-54834-4-zsE7lyGqsU@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).