[cfe-dev] Problem with relinking

[Don Hinton via cfe-dev]

Thanks.  That showed that the lib was older than the cpp that got compiled
and linked into it.  Perhaps it's just clock skew -- the power here goes
out all the time, so my wifi is pretty iffy right now.

thanks for the tip...
don

On Wed, Mar 27, 2019 at 1:13 AM Paweł Sikora via cfe-dev <
cfe-dev at lists.llvm.org> wrote:

> On 27.03.2019 01:34, Don Hinton via cfe-dev wrote:
> > Hi Tom:
> >
> > I've got a smaller test case which only involves part of
> > clang-tools-extra.  At least it's only a few files that get relinked,
> > but when I make a change to an llvm file, it relinks 90+ binaries.
> >
> > I only need to touch a file in my new checker to get this behavior.  If
> > I run ninja after touching a file, it'll recompile that file, then
> > relink everything in clang-tidy.  And if I run ninja again, without
> > doing anything else, it will relink all the same binaries:
> >
> > local:/Users/dhinton/projects/llvm_project/monorepo/build/Debug $ ninja
> > [11/11] Linking CXX executable bin/c-index-test
> > local:/Users/dhinton/projects/llvm_project/monorepo/build/Debug $ ninja
> > [10/10] Linking CXX executable bin/c-index-test
> >
> > Still now sure what's going on...
>
> hi,
>
> try to use 'ninja -j1 -d explain' and check 'older than recent most
> input' logs.
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20190327/5eda97fc/attachment.html>