Re: Reply headers vs. in-mail requests (was Re: Bad news to CUDA applications (was: Re: GCC 6 & binutils for the Debian stretch release))

2016-07-01 Thread Jonathan Dowland
On Fri, Jul 01, 2016 at 09:04:50AM -0400, The Wanderer wrote: > I'm pretty sure there is no header setting which will make this fully > automatic. I have been suitably admonished off-list for starting this $DEITY-awful sub-topic once again. Consider myself chastened! -- Jonathan Dowland Please

Reply headers vs. in-mail requests (was Re: Bad news to CUDA applications (was: Re: GCC 6 & binutils for the Debian stretch release))

2016-07-01 Thread The Wanderer
On 2016-07-01 at 08:43, Jonathan Dowland wrote: > On Fri, Jul 01, 2016 at 06:07:27AM +, lumin wrote: > >> (please keep me in CC list) > > I suggest setting the headers to make this automatic rather than > asking people to remember to do it :) I'm pretty sure there is no header setting which

Re: Bad news to CUDA applications (was: Re: GCC 6 & binutils for the Debian stretch release)

2016-07-01 Thread Jonathan Dowland
On Fri, Jul 01, 2016 at 06:07:27AM +, lumin wrote: > (please keep me in CC list) I suggest setting the headers to make this automatic rather than asking people to remember to do it :) > I'm pointing out a BIG problem introduced by stretch's GCC-6-only plan. > > In brief CUDA 8.0~RC fails to

Re: Bad news to CUDA applications (was: Re: GCC 6 & binutils for the Debian stretch release)

2016-07-01 Thread Vincent Danjean
Le 01/07/2016 à 08:51, lumin a écrit : > > Releated bug on ArchLinux: > https://bugs.archlinux.org/task/49272?project=5&opened=12602 > > There are some hacks but none of them seems to be "an actual solution > to packaging". Personally, I would create a gcc/g++ wrapper in order to capture the exa

Re: Bad news to CUDA applications (was: Re: GCC 6 & binutils for the Debian stretch release)

2016-07-01 Thread lumin
Releated bug on ArchLinux: https://bugs.archlinux.org/task/49272?project=5&opened=12602 There are some hacks but none of them seems to be "an actual solution to packaging". On Fri, 2016-07-01 at 06:07 +, lumin wrote: > Hi all, > (please keep me in CC list) > > I'm pointing out a BIG problem

Bad news to CUDA applications (was: Re: GCC 6 & binutils for the Debian stretch release)

2016-06-30 Thread lumin
Hi all, (please keep me in CC list) I'm pointing out a BIG problem introduced by stretch's GCC-6-only plan. In brief CUDA 8.0~RC fails to work with GCC-6, this conclusion comes from my local Caffe build log as attached. That is to say, after GCC-6 transition *ALL* packages depending on cuda will

Re: GCC 6 & binutils for the Debian stretch release

2016-06-28 Thread James McCoy
On Fri, Jun 24, 2016 at 04:03:44PM +0200, Paul Wise wrote: > On Fri, Jun 24, 2016 at 3:46 PM, Matthias Klose wrote: > > > As announced a year ago [1], GCC 6 will be the default GCC for the Debian > > stretch release. GCC 6 is now available in testing, and can be made the > > default > > by insta

Re: GCC 6 & binutils for the Debian stretch release

2016-06-24 Thread Paul Wise
On Fri, Jun 24, 2016 at 3:46 PM, Matthias Klose wrote: > As announced a year ago [1], GCC 6 will be the default GCC for the Debian > stretch release. GCC 6 is now available in testing, and can be made the > default > by installing the gcc/g++ packages from experimental. Known build failures >