1 |
sys-devel/gcc runs tests, but the results are ignored and I remember the |
2 |
tests fail most of the time. |
3 |
|
4 |
Because the tests take long time to run and fail anyway (I understand |
5 |
it's non-trivial to fix those on Gentoo side), I wonder whether it makes |
6 |
sense to run them at all: |
7 |
|
8 |
toolchain.eclass: |
9 |
|
10 |
gcc_src_test() { |
11 |
cd "${WORKDIR}"/build |
12 |
emake -j1 -k check || ewarn "check failed and that sucks :(" |
13 |
} |
14 |
|
15 |
My suggestion is to make the src_test empty (I think the default one |
16 |
still calls make). I can produce a patch if needed. |
17 |
|
18 |
What do you think? |