On Tue, 2007-01-02 at 15:43 -0800, Adam Nemet wrote:
If it is not too late I'd prefer the latter. If I understand the
problem correctly the former would still fail if the test user is not
privileged enough to recreate the directory structure under /.
Yes, that is correct. OK, having given
Ben Elliston [EMAIL PROTECTED] writes:
I see a couple of solutions, but would like to discuss them here before
working on a patch:
1. have the bprob.exp test driver create the appropriate directory
tree on the target (and remove it when finished); or
2. set GCOV_PREFIX when running the
On Thu, Dec 21, 2006 at 10:00:47AM +1100, Ben Elliston wrote:
On Thu, 2006-12-21 at 09:56 +1100, Ben Elliston wrote:
After some digging, I managed to work out why: the gcov runtime code
wants to create the .gcda file in the same directory that the object
file was created on the build
While testing a cross-compiler, I had to track down a handful of
failures in gcc.misc-tests/bprob.exp and g++.dg/bprop/bprob.exp. The
test harness was reporting that the .gcda data files were not being
created after running the instrumented test case.
After some digging, I managed to work out
On Thu, 2006-12-21 at 09:56 +1100, Ben Elliston wrote:
After some digging, I managed to work out why: the gcov runtime code
wants to create the .gcda file in the same directory that the object
file was created on the build system. Unless the same directory
structure exists on the target, the
