On Wed, Nov 11, 2015 at 9:30 AM, Sekenre <[email protected]> wrote > > > It works! I got audio and networking operational. (still have problems > with virtual hard disk, but that's just kernel module options, not build > related) >
Great! > > Changing the kernel caused a rebuild of everything including GCC! How > would I go about discovering why? > Hmm, that doesn't sound right. Is it reproduceable? If it's a specific file in the kernel that is causing a rebuild, you might be able to get some information out of 'tup graph'. Eg: 'tup graph linux/fs/ext3/bitmap.c' shows everything that will be built if bitmap.c changes. However, I don't see GCC rebuilding when doing so. Also it isn't easy at the moment to use 'tup graph' to go backwards through the graph... ie: to graph gcc and everything that would cause it to be rebuilt. This might be a useful addition though for investigating things like this. > > How would I go about upgrading an underlying package (eg openssh), would I > just pull from the source repository and then rebase the gittup.org > specific stuff on top? > > Yeah, that sounds reasonable. For openssh it looks like I probably compiled it in make to see what the command-lines looked like, and then extracted the necessary pieces into the Tupfile. So you may have to do a kind of manual three-way merge to see what changes were made to the Makefile, and make the appropriate changes to the Tupfile. -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.
