Bug#807579: CUDA 7.5 planning

2016-03-08 Thread Andreas Beckmann
On 2016-03-08 17:01, Graham Inggs wrote:
> On 08/03/2016 17:50, Andreas Beckmann wrote:
>> On 2016-03-08 16:13, Graham Inggs wrote:
>> which doesn't sound that useful without Xorg driver ...
> 
> You mean nvidia-settings doesn't sound that useful without Xorg driver?
> Quite possibly, but libxnvctrl0 is built by the nvidia-settings source,
> maybe that might be useful?

In Debian we moved src:nvidia-settings to main and build libxnvctrl0 on
all platforms ... Ubuntu might differ here ... oh yes, we wanted to
unify the packaging at some point ...

>>> pycuda failed with 'cannot find -lcuda', probably due to missing
>>> libcuda1
>>
>> Is that a nvcc or a gcc command failing? nvcc should be able to resolve
>> -lcuda via the stub (the corresponding -L... are set in nvcc.profile,
>> but I haven't tested this (w/o libcuda1)).
> 
> I think it's gcc, the build log is here:

looks like this, so this failure should go away with libcuda1 replacing
no-libcuda1 ...

I'll probably upload 7.5 to experimental/NEW tonight.


Andreas



Bug#807579: CUDA 7.5 planning

2016-03-08 Thread Graham Inggs

On 08/03/2016 17:50, Andreas Beckmann wrote:

On 2016-03-08 16:13, Graham Inggs wrote:
which doesn't sound that useful without Xorg driver ...


You mean nvidia-settings doesn't sound that useful without Xorg driver?
Quite possibly, but libxnvctrl0 is built by the nvidia-settings source, 
maybe that might be useful?



pycuda failed with 'cannot find -lcuda', probably due to missing libcuda1


Is that a nvcc or a gcc command failing? nvcc should be able to resolve
-lcuda via the stub (the corresponding -L... are set in nvcc.profile,
but I haven't tested this (w/o libcuda1)).


I think it's gcc, the build log is here:

https://launchpad.net/~ginggs/+archive/ubuntu/testing/+build/9316956/+files/buildlog_ubuntu-xenial-ppc64el.pycuda_2015.1.3-1build3~ppa3_BUILDING.txt.gz



Bug#807579: CUDA 7.5 planning

2016-03-08 Thread Andreas Beckmann
On 2016-03-08 16:13, Graham Inggs wrote:
> In Ubuntu on ppc64el:
> 
> eztrace-contrib built without changes
> hwloc-contrib built without changes, after building nvidia-settings for
> ppc64el

which doesn't sound that useful without Xorg driver ...

> starpu-contrib built after enabling Architecture: any
> 
> pycuda failed with 'cannot find -lcuda', probably due to missing libcuda1

Is that a nvcc or a gcc command failing? nvcc should be able to resolve
-lcuda via the stub (the corresponding -L... are set in nvcc.profile,
but I haven't tested this (w/o libcuda1)).


Andreas



Bug#807579: CUDA 7.5 planning

2016-03-08 Thread Graham Inggs

In Ubuntu on ppc64el:

eztrace-contrib built without changes
hwloc-contrib built without changes, after building nvidia-settings for 
ppc64el

starpu-contrib built after enabling Architecture: any

pycuda failed with 'cannot find -lcuda', probably due to missing libcuda1



Bug#807579: CUDA 7.5 planning

2016-03-08 Thread Graham Inggs

On 08/03/2016 14:47, Andreas Beckmann wrote:

OK, I added back the virtual package, it's used on Ubuntu only (but
provided everywhere). Untested. Does this work for you?


That's great, thank you!



Bug#807579: CUDA 7.5 planning

2016-03-08 Thread Andreas Beckmann
On 2016-03-08 12:30, Graham Inggs wrote:
> I was able to build the reverse-dependencies eztrace-contrib,
> hwloc-contrib and pycuda without modification.

Good to know!

>> Looking at ppc64el now ...
> 
> For Ubuntu, I think I will use the no-libcuda1 virtual package for
> ppc64el.  I don't think a Tesla driver package for ppc64el will be
> uploaded in time for the Xenial release.

OK, I added back the virtual package, it's used on Ubuntu only (but
provided everywhere). Untested. Does this work for you?


Andreas



Bug#807579: CUDA 7.5 planning

2016-03-08 Thread Graham Inggs

On 01/03/2016 18:15, Andreas Beckmann wrote:

amd64 should be more or less ready for going to experimental, more
testing would be welcome!
I tried the cuda code samples (see README.Debian), and most built (only
those few that link with -lcudadevrt seem to miss a -lcudart). I didn't
try to actually run even one of them :-)


I built 7.5.18-1 r6291 in an Ubuntu PPA.
I was able to build the reverse-dependencies eztrace-contrib, 
hwloc-contrib and pycuda without modification.


A local build of pycuda on Ubuntu Xenial failed with the following 
error, but it probably just picked up something else installed:


error: Cython does not appear to be installed

I tried a couple of the pycuda examples and they ran successfully, but 
the script to download more examples from the wiki didn't seem to work 
any more.


Ubuntu has starpu-contrib 1.1.5-0.  It build successfully after I 
changed CONTRIB_GCC_VERSION := 5 and adjusted the build-dependencies.

I did not try building with CONTRIB_GCC_VERSION  := 4.9.


Looking at ppc64el now ...


For Ubuntu, I think I will use the no-libcuda1 virtual package for 
ppc64el.  I don't think a Tesla driver package for ppc64el will be 
uploaded in time for the Xenial release.




Bug#807579: CUDA 7.5 planning

2016-03-01 Thread Andreas Beckmann
On 2016-03-01 06:25, lumin wrote:
> Is there something that I can help?
> 
> Besides please ping me if the svn repo is ready,
> I can conduct some test and check :-)

amd64 should be more or less ready for going to experimental, more
testing would be welcome!
I tried the cuda code samples (see README.Debian), and most built (only
those few that link with -lcudadevrt seem to miss a -lcudart). I didn't
try to actually run even one of them :-)

What's the status of using CUDA 7.5 with GCC 6 (already in experimental)?
Right now I blocked this version in the header check and the gcc/g++
wrappers also ignore that version, so you need to ensure you are really
testing with g++-6. If it doesn't blow up, we should enable it as well.

Looking at ppc64el now ...


Andreas



Bug#807579: CUDA 7.5 planning

2016-02-29 Thread lumin
Hi anbe,

Is there something that I can help?

Besides please ping me if the svn repo is ready,
I can conduct some test and check :-)

Thanks.
-- 
 .''`.
: :' :
`. `' 
  `-