Update: I re-initialized my tup repository and the behavior remained, so it wasn't the variants, it is a "new" tup behavior.
In the repo, "@tupjob" shows up starting way back in 2011, and I've been using a rmore recent version than that... For some reason my compilation targets are not getting put into these (chrooted?) @tupjob directories, only my link steps. But of course tup shouldn't know what steps are building and which are linking; so is this out-of-source build behavior triggered by cross-directory dependencies? On Wed, May 7, 2014 at 6:33 PM, Andrew Wagner <[email protected]> wrote: > Hello, > > When I hit linker errors, vim is getting confused by some out-of-source > building tup is doing: > > /home/awagner/planepower/.tup/mnt/@tupjob-27971/home/awagner/planepower/bbones/server/main_server.c|74| > undefined reference to `pthread_create' > > Vim has no idea that temp dir is associated with the file in my repo, and > is consequently unable to jump there. I tried -j1 and the build is still > happening in a temp dir. > > Is there a quick way to disable building in a temp directory (i.e. with a > flag or with an environment variable)? > > This may be caused by a change that is quite old; I updated tup from the > git repo today for the first time in many months. I am not currently using > variants, although I did create and destroy one today for the first time, > so if that changes tup's state, it may also be causing it. > > Cheers, > Andrew > > -- -- 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.
