Hello Michael:
Firstly, thank you very much for always providing your aid to me for
microblaze.
At present, after try testsuite, the result is much better than my
original trying, please help check the result: "is it enough for our
microblaze testsuite" (can we say it pass checking)?
Current result:
# of expected passes 65987
# of unexpected failures 82
# of unexpected successes 1
# of expected failures 97
# of unresolved testcases 16378
# of unsupported tests 1810
Original result:
# of expected passes 48408
# of unexpected failures 17253
# of unexpected successes 1
# of expected failures 97
# of unresolved testcases 16570
# of unsupported tests 1854
After check the current result log, I find many remote target test
related sentences, do we have to process it?
e.g. "Download to microblaze-xilinx-gdb failed, couldn't execute "rcp": no
such file or directory."
>>
>> And I guess, it is a glibc bug: which still add root directory (e.g.
>> /upstream/release) in 'libc.so' when already has --with-sysroot for
>> configure.
>>
>
> Oh, sorry, glibc should also need --with-sysroot. I shall try it today,
> hope it will let all things OK.
>
After add --with-sysroot for glibc, this issue is still existance. And I
remove the redundant direcltory manually for libc.so and libpthread.so.
If our microblaze testsuite is OK, I will skip this issue (since I have
no enough time resource on glibc, at present).
Thanks.
--
Chen Gang
Open share and attitude like air water and life which God blessed
