On Thu, 19 Oct 2017 10:37:14 +0200 Richard Biener <richard.guent...@gmail.com> wrote:
> On Wed, Oct 18, 2017 at 11:58 PM, FX <fxcoud...@gmail.com> wrote: > >> Could you test using .PHONY: install-headers instead? > >> That target *is* phony, so telling make that seems sensible. > > > > I’ve tried adding it to the existing .PHONY list: > > > > Index: libstdc++-v3/include/Makefile.in > > =================================================================== > > --- libstdc++-v3/include/Makefile.in (revision 253855) > > +++ libstdc++-v3/include/Makefile.in (working copy) > > @@ -1449,6 +1449,7 @@ uninstall-am: > > distclean-libtool dvi dvi-am html html-am info info-am install \ > > install-am install-data install-data-am install-data-local \ > > install-dvi install-dvi-am install-exec install-exec-am \ > > + install-freestanding-headers install-headers \ > > install-html install-html-am install-info install-info-am \ > > install-man install-pdf install-pdf-am install-ps \ > > install-ps-am install-strip installcheck installcheck-am \ > > > > > > But that doesn’t work: > > > > In file included > > from > > /Users/fx/devel/gcc/ibin/x86_64-apple-darwin17.0.0/i386/libstdc++-v3/include/bits/exception_ptr.h:39:0, > > from /Users/fx/devel/gcc/trunk/libstdc++-v3/libsupc++/exception:143, > > from > > /Users/fx/devel/gcc/ibin/x86_64-apple-darwin17.0.0/i386/libstdc++-v3/include/ios:39, > > from > > /Users/fx/devel/gcc/ibin/x86_64-apple-darwin17.0.0/i386/libstdc++-v3/include/istream:38, > > from > > /Users/fx/devel/gcc/ibin/x86_64-apple-darwin17.0.0/i386/libstdc++-v3/include/sstream:38, > > from > > /Users/fx/devel/gcc/ibin/x86_64-apple-darwin17.0.0/i386/libstdc++-v3/include/complex:45, > > from > > /Users/fx/devel/gcc/ibin/x86_64-apple-darwin17.0.0/i386/libstdc++-v3/include/ccomplex:39, > > from > > /Users/fx/devel/gcc/trunk/libstdc++-v3/include/precompiled/stdc++.h:52: > > /Users/fx/devel/gcc/trunk/libstdc++-v3/libsupc++/typeinfo:36:10: > > fatal error: bits/hash_bytes.h: No such file or directory #include > > <bits/hash_bytes.h> > > ^~~~~~~~~~~~~~~~~~~ > > So the issue is PCH generation (why's that re-generated at install time?). May be indeed: I have a lot parallel builds and never see problem like this, but I skip PCH generation. -- - ptr
