There is no reason for libbacktrace to try to include files from
../gcc/include. All the required header files can now be found in
libgcc. I'm not sure why I added the -I ../gcc/include in the first
place; perhaps I was thinking of code from before the libgcc migration.
Using -I ../gcc/include can in some unusual cases lead to the
difficulties described in PR 54834. This patch fixes the problem.
Bootstrapped and ran libbacktrace testsuite on
x86_64-unknown-linux-gnu. Committed to mainline.
Ian
2013-01-01 Ian Lance Taylor <i...@google.com>
PR bootstrap/54834
* Makefile.am (AM_CPPFLAGS): Remove -I ../gcc/include and -I
$(MULTIBUILDTOP)/../../gcc/include.
* Makefile.in: Rebuild.
Index: Makefile.am
===================================================================
--- Makefile.am (revision 194764)
+++ Makefile.am (working copy)
@@ -32,7 +32,7 @@
ACLOCAL_AMFLAGS = -I .. -I ../config
AM_CPPFLAGS = -I $(top_srcdir)/../include -I $(top_srcdir)/../libgcc \
- -I ../libgcc -I ../gcc/include -I $(MULTIBUILDTOP)../../gcc/include
+ -I ../libgcc
AM_CFLAGS = $(EXTRA_FLAGS) $(WARN_FLAGS) $(PIC_FLAG)
