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
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
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
Le 01/07/2016 à 08:51, lumin a écrit :
>
> Releated bug on ArchLinux:
> https://bugs.archlinux.org/task/49272?project=5=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 exact
Releated bug on ArchLinux:
https://bugs.archlinux.org/task/49272?project=5=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
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
6 matches
Mail list logo
