Hi! I just started to use tup these days and ran into the xcrun_db issue mentioned in this thread. Every time after I boot the machine I will need to manually invoke clang so that the paths of the clang toolchain are cached, otherwise tup upd will fail. Is this issue fixed? Or is it possible to tell tup to ignore certain outputs?
[email protected]於 2013年12月7日星期六 UTC-5上午11時15分07秒寫道： > > On Fri, Dec 6, 2013 at 8:30 PM, comex <[email protected] <javascript:>> > wrote: > >> On Fri, Dec 6, 2013 at 4:59 PM, Mike Shal <[email protected] <javascript:>> >> wrote: >> > Is it reproduceable for you? I hit the same error the first time I run >> the >> > test after booting, but after that the test seems to run fine. Maybe it >> > should just ignore writes to '/var/*/xcrun_db'? >> >> FYI, xcrun_db is what the wrapper binary at /usr/bin/nm is using to >> cache the path of the real nm; this applies to everything in the >> toolchain, including clang. Without a cache, it takes an impressive >> 0.18s each time just to decide what to invoke, so I'd avoid dropping >> such writes. >> > > Ahh, thanks for the info. By "ignore" I meant it would detect & allow the > write to go through, but not count it as an actual output when it goes to > check the actual vs. expected outputs. So xcrun_db should still be written, > just that tup wouldn't complain about it the first time it runs something > in the toolchain. Would that work? > > -Mike > -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
