That patch solved the problem Andreas, thank you very much! Should we file a PR to request to integrate this patch? Or should I better follow Peter's suggestion to build gcc from a separate build directory?
Best regards. 2015-04-14 18:14 GMT+02:00 Andreas Schwab <sch...@suse.de>: > Please try this patch: > > diff --git a/libcc1/Makefile.am b/libcc1/Makefile.am > index ecab22c..7a274b3 100644 > --- a/libcc1/Makefile.am > +++ b/libcc1/Makefile.am > @@ -17,7 +17,7 @@ > ## <http://www.gnu.org/licenses/>. > > ACLOCAL_AMFLAGS = -I .. -I ../config > -gcc_build_dir = ../$(host_subdir)/gcc > +gcc_build_dir = ../gcc > AM_CPPFLAGS = -I $(srcdir)/../include -I $(srcdir)/../libgcc \ > -I $(gcc_build_dir) -I$(srcdir)/../gcc \ > -I $(srcdir)/../gcc/c -I $(srcdir)/../gcc/c-family \ > diff --git a/libcc1/Makefile.in b/libcc1/Makefile.in > index ce752c0..1916134 100644 > --- a/libcc1/Makefile.in > +++ b/libcc1/Makefile.in > @@ -245,7 +245,7 @@ top_builddir = @top_builddir@ > top_srcdir = @top_srcdir@ > visibility = @visibility@ > ACLOCAL_AMFLAGS = -I .. -I ../config > -gcc_build_dir = ../$(host_subdir)/gcc > +gcc_build_dir = ../gcc > AM_CPPFLAGS = -I $(srcdir)/../include -I $(srcdir)/../libgcc \ > -I $(gcc_build_dir) -I$(srcdir)/../gcc \ > -I $(srcdir)/../gcc/c -I $(srcdir)/../gcc/c-family \ > -- > 2.3.5 > > > Andreas. > > -- > Andreas Schwab, SUSE Labs, sch...@suse.de > GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 > "And now for something completely different." -- "People say nothing is impossible, but I do nothing everyday." - A. A. Milne
