On Mon, Jul 21, 2014 at 6:07 PM, Casey Rodarmor <[email protected]> wrote:
Hi all, > > I have a project where turning on the "-g" to clang causes the build to > fail. > > The first rule of the tupfile (attached) builds a pch from the "common.h" > header file. When I uncomment "#CXXFLAGS += -g", I get a bunch of errors > like the following: > > * 2) cc view.program.c++ > fatal error: cannot open file > '/Users/rodarmor/pkg/rmr/src/.tup/mnt/@tupjob-1831/Users/rodarmor/pkg/rmr/src/common.h': > Operation not permitted > 1 error generated. > *** tup errors *** > *** Command ID=1631 failed with return value 1 > tup error: Expected to write to file 'view.program.o' from cmd 1631 but > didn't > *** Additionally, command 1631 failed to process input dependencies. > These should probably be fixed before addressing the command failure. > > I think that "-g" is making clang all of a sudden look for symbols in > common.h, which it can't open. Is that what's actually happening, and any > ideas on how to fix it? > > Hi Casey, I can't seem to reproduce this particular behavior (maybe it is specific to the version of clang? I have 3.4.) However, usually when the .tup/mnt paths are getting stuck in the process, the workaround is to use the ^c flag in your rule. This runs the process in a chroot, so it doesn't see the .tup/mnt path. There are longer-term plans to make this not necessary, but that should work around it for now. -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.
