While seemingly independent, the latter really depends on the former, or else the fuzzing harness build's behavior would be dependent upon the test harness having been built (and hence x86_emulate/ there being absent / present, offering source files [as symlinks] which really should be taken from the xen/ subtree).
1: test: use vpath uniformly for access to code living elsewhere 2: fuzz: use vpath uniformly for access to code living elsewhere Jan
