Re: unwind.h installation causes rebuilds
On May 25, 2012, at 17:17 , Michael Matz wrote: >> This should have been fixed by rev 187839 ... > Super, yes, that works. Great :) > Though I still wonder if the whole copy-over-to-gcc business shouldn't be > dependend on anything newly built. I can't see the use in copying > over the same unchanged files to a place where they already are. > And generally installing with -p also can't hurt, can it? I suppose not but don't know the full story here.
Re: unwind.h installation causes rebuilds
Hi, On Fri, 25 May 2012, Olivier Hainque wrote: > > I've noticed that libitm is always rebuild with a non-bootstrap tree even > > with merely a sequence of two makes. The reason turns out to be that > > installation of unwind.h from libgcc, which is always done with a simple > > make: > > This should have been fixed by rev 187839 after the thread > initiated at > > http://gcc.gnu.org/ml/gcc-patches/2012-05/msg01596.html > > Could you please tell if that works for you ? Super, yes, that works. Though I still wonder if the whole copy-over-to-gcc business shouldn't be dependend on anything newly built. I can't see the use in copying over the same unchanged files to a place where they already are. And generally installing with -p also can't hurt, can it? Ciao, Michael.
Re: unwind.h installation causes rebuilds
Hello Michael, On May 25, 2012, at 16:30 , Michael Matz wrote: > I've noticed that libitm is always rebuild with a non-bootstrap tree even > with merely a sequence of two makes. The reason turns out to be that > installation of unwind.h from libgcc, which is always done with a simple > make: This should have been fixed by rev 187839 after the thread initiated at http://gcc.gnu.org/ml/gcc-patches/2012-05/msg01596.html Could you please tell if that works for you ? Thanks in advance, Olivier
