libbacktrace patch committed: Don't use -I ../gcc/include

Submitted by Ian Taylor on Jan. 1, 2013, 4:23 p.m.


Message ID
State New
Headers show

Commit Message

Ian Taylor Jan. 1, 2013, 4:23 p.m.
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.


2013-01-01  Ian Lance Taylor  <>

	PR bootstrap/54834
	* (AM_CPPFLAGS): Remove -I ../gcc/include and -I
	* Rebuild.

Patch hide | download patch | download mbox

---	(revision 194764)
+++	(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