public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tobi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/54834] bootstrap fails when building libbacktrace
Date: Sat, 13 Oct 2012 10:42:00 -0000 [thread overview]
Message-ID: <bug-54834-4-pud0xrKLUY@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
Tobias Schlüter <tobi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
--- Comment #6 from Tobias Schlüter <tobi at gcc dot gnu.org> 2012-10-13 10:41:44 UTC ---
I'm opening this again, as I find the same problem again after updating my git
tree, so it's not due to some changed dependencies in the libbacktrace merge:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../libbacktrace -I
../../libbacktrace/../include -I ../../libbacktrace/../libgcc -I ../libgcc -I
../gcc/include -I ../../gcc/include -funwind-tables -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-Wmissing-format-attribute -Wcast-qual -Werror -g -c ../../libbacktrace/state.c
-o state.o
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../libbacktrace -I
../../libbacktrace/../include -I ../../libbacktrace/../libgcc -I ../libgcc -I
../gcc/include -I ../../gcc/include -funwind-tables -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-Wmissing-format-attribute -Wcast-qual -Werror -g -c
../../libbacktrace/simple.c -o simple.o
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../libbacktrace -I
../../libbacktrace/../include -I ../../libbacktrace/../libgcc -I ../libgcc -I
../gcc/include -I ../../gcc/include -funwind-tables -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-Wmissing-format-attribute -Wcast-qual -Werror -g -c
../../libbacktrace/backtrace.c -o backtrace.o
In file included from ../../libbacktrace/backtrace.c:35:
../gcc/include/unwind.h:48: error: unknown machine mode 'unwind_word'
In file included from ../../libbacktrace/simple.c:35:
../gcc/include/unwind.h:48: error: unknown machine mode 'unwind_word'
../gcc/include/unwind.h:49: error: unknown machine mode 'unwind_word'
../gcc/include/unwind.h:49: error: unknown machine mode 'unwind_word'
In file included from ../../libbacktrace/simple.c:35:
../gcc/include/unwind.h:252:4: error: #error "__SIZEOF_LONG__ macro not
defined"
../gcc/include/unwind.h:256:4: error: #error "__SIZEOF_POINTER__ macro not
defined"
In file included from ../../libbacktrace/backtrace.c:35:
../gcc/include/unwind.h:252:4: error: #error "__SIZEOF_LONG__ macro not
defined"
../gcc/include/unwind.h:256:4: error: #error "__SIZEOF_POINTER__ macro not
defined"
make[4]: *** [simple.lo] Error 1
make[4]: *** Waiting for unfinished jobs....
make[4]: *** [backtrace.lo] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all-stage1-libbacktrace] Error 2
make[1]: *** [stage1-bubble] Error 2
make: *** [all] Error 2
I could fix this by deleting all occurences of unwind.h in the build tree. I
therefore assume that some dependencies are broken.
next prev parent reply other threads:[~2012-10-13 10:42 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 [this message]
2012-11-01 10:14 ` nico at josuttis dot de
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-pud0xrKLUY@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).