Hi Lumin,
>I will keep those custom target in the bottom of d/rules.
>Yes, all of custom-target-related lines had been already
>clustered at the bottom of d/rules, and I have drew a big
>split line at the beginning of them, in the updated version.
wonderful!
>
>The custom stuff is explained in the README.Debian, and it
>in fact includes a custom compile guide and some more other
>things.
ok
>I have added g{cc,++}-4.9 in the updated d/control, so this package
>won't FTBFS due to dependency bump of build-essential to gcc5.
>
>However if CUDA/experimental is an updated version (7.0),
>gcc5 should be able to work.
>(I successfully built Caffe on ArchLinux + CUDA 7 + gcc 5)
so maybe we can just wait for cuda to go in unstable, right?
gcc-5 migrated tonight, so I guess it is just a matter of days
>I think this is better than above:
>
>19 ifeq (installed, $(shell dpkg -s nvidia-cuda-toolkit | grep -o installed))
>20 flag_build_caffe_cuda := y
>21 endif
I stolen the bits for my hedgewars packaging
(honestly in buildds there is no "leftover config", but well, on users
machines yes, there might be!
thanks a lot for the tip :)
so let's wait for the build failures and maybe to build against gcc-5.
BTW yes, the qemu and aptitude errors are related to qemu virtualization (some
calls
are not implemented), and some DoM error :)
I guess amd64 and i386 are the two architectures that are worth a try for this
package.
cheers,
G.
