Bug#861497: marked as done (gcc-6-cross: FTBFS in stretch)

2017-05-07 Thread Debian Bug Tracking System
Your message dated Mon, 8 May 2017 01:46:05 +0200 with message-id <20170507234605.7h22xnifatajas6d@nuc> and subject line Re: Bug#861497: gcc-6-cross: FTBFS in stretch has caused the Debian Bug report #861497, regarding gcc-6-cross: FTBFS in stretch to be marked as done. This means that you claim t

Results for 8.0.0 20170505 (experimental) [trunk revision 247636] (Debian 20170505-1) testsuite on arm-unknown-linux-gnueabi

2017-05-07 Thread Matthias Klose
LAST_UPDATED: Fri May 5 15:03:06 UTC 2017 (revision 247636) Native configuration is arm-unknown-linux-gnueabi === libatomic tests === Running target unix === libatomic Summary === # of expected passes44 # of unsupported tests 5

Results for 8.0.0 20170505 (experimental) [trunk revision 247636] (Debian 20170505-1) testsuite on mips64el-unknown-linux-gnuabi64

2017-05-07 Thread Matthias Klose
LAST_UPDATED: Fri May 5 15:03:06 UTC 2017 (revision 247636) === acats tests === FAIL: cb1010a === acats Summary === # of expected passes2319 # of unexpected failures1 Native configuration is mips64el-unknown-linux-gnuabi64 ==

Results for 8.0.0 20170505 (experimental) [trunk revision 247636] (Debian 20170505-1) testsuite on mipsel-unknown-linux-gnu

2017-05-07 Thread Matthias Klose
LAST_UPDATED: Fri May 5 15:03:06 UTC 2017 (revision 247636) === acats tests === === acats Summary === # of expected passes2320 # of unexpected failures0 Native configuration is mipsel-unknown-linux-gnu === g++ tests === Runni

Results for 8.0.0 20170505 (experimental) [trunk revision 247636] (Debian 20170505-1) testsuite on arm-unknown-linux-gnueabihf

2017-05-07 Thread Matthias Klose
LAST_UPDATED: Fri May 5 15:03:06 UTC 2017 (revision 247636) Native configuration is arm-unknown-linux-gnueabihf === libatomic tests === Running target unix === libatomic Summary === # of expected passes44 # of unsupported tests 5

Re: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

2017-05-07 Thread Samuel Thibault
Hello, Lumin, on dim. 07 mai 2017 02:29:46 +, wrote: > I'm not sure whether this bug should be marked as serious. Since your test > cases are mixing the default cc (GCC-6) and clang-3.8 together. Well, there is no choice about this: not doing so leads to: cc-c -o test.o test.c nvcc -c t