UBUNTU 18.10 GUAKE HOW TO
There are many instructions available on the web concerning how to “downgrade” your installed GCC version. If you manually build a gcc 7.x version, just make sure that version gets selected first on your PATH, and you should be able to build the samples.
UBUNTU 18.10 GUAKE INSTALL
(and you would need to “clean out” the old install - refer to the linux install guide)įinally, in your current setup, you should be able to manually build a gcc 7.x version that will work with CUDA 10 and at least may get you past this issue (although there may be other compatibility problems with Ubuntu 18.10). You should be able to use Ubuntu 18.04 as your OS instead.Īlternatively, you could try the runfile installer on Ubuntu 18.10, but I don’t know if that will work either. I guess you are trying to use the Ubuntu 18.04 deb local installer here. Ubuntu 18.10 isn’t a supported OS for CUDA. #error - unsupported GNU version! gcc versions later than 7 are not supported! Tried to run make on the samples after this but it throws the following error saying unsupported compiler, nothing later than 7 supported as shown below /usr/local/cuda-10.0/bin/./targets/x86_64-linux/include/crt/host_config.h:129:2: error: #error - unsupported GNU version! gcc versions later than 7 are not supported! Nvcc -V output nvcc: NVIDIA (R) Cuda compiler driverĬopyright (c) 2005-2018 NVIDIA CorporationĬuda compilation tools, release 10.0, V10.0.130 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) The following NEW packages will be installed:īuild-essential cuda cuda-10-0 cuda-command-line-tools-10-0 cuda-compiler-10-0 cuda-cupti-10-0 cuda-demo-suite-10-0 cuda-documentation-10-0 cuda-drivers cuda-nvcc-10-0 cuda-runtime-10-0 cuda-samples-10-0Ġ upgraded, 21 newly installed, 0 to remove and 0 not upgraded.Īfter this operation, 580 MB of additional disk space will be used.Īfter installation NVRM version: NVIDIA UNIX x86_64 Kernel Module 410.73 Sat Oct 20 22:12: Libasan5-dbg liblsan0-dbg libtsan0-dbg libubsan1-dbg libmpx2-dbg libquadmath0-dbg Menu g++-multilib g++-8-multilib gcc-8-doc libstdc++6-8-dbg gcc-multilib autoconf automake libtool flex bison gcc-doc gcc-8-multilib gcc-8-locales libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg The following additional packages will be installed:īuild-essential cuda-10-0 cuda-command-line-tools-10-0 cuda-compiler-10-0 cuda-cupti-10-0 cuda-demo-suite-10-0 cuda-documentation-10-0 cuda-drivers cuda-nvcc-10-0 cuda-runtime-10-0 cuda-samples-10-0Ĭuda-toolkit-10-0 cuda-tools-10-0 dkms g++ g++-8 gcc gcc-8 nvidia-dkms-410 nvidia-driver-410 It's been beaten by ill-informed people repeating poorly understood talking points.Successfully installed CUDA 10(.deb local) but it installed gcc-8 as dependency as you can see below Reading package lists. I'm not going to repeat them all here (because who has the time), this horse has been beaten to death so often it is now a goo of red puree mushed into the carpets If gnome have done a shit job of actually using the features that X has had for the last decade or more, blame gnome, not X. It's impossible for an actave grab to interpose. Look: the modern X architecture routes EVERYTHING through the compositor just like Wayland. The inability to use most of the buttons on a laptop while a locked session is in progress (but yes having to open up and login to a device just to hit the volume down key is totally what we expect from modern 2018 systems).Īh yes, the thing that isn't an issue with a modern compositor architecture. Note: if the desktpos don't implement that, it's their fault not an inherent limitation in X. Oh you mean the issue that doesn't happen at all if you use a compositor like 99% of modern desktops. The issues on on exclusive access that creates a huge security issue for lockscreens It's been a very VERY long time since I've run a 20MHz desktop CPU. Sure it was slow on a Sun 3/60 and people were maybe right to whine then. Yes indeed, forget that because there's no evidence X is slow.
0 kommentar(er)
