-
Hi |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
By libgcc1-8, are you talking about shared libraries for the gcc runtime? The gcc-for-nvcc recipes explicitly disable the shared runtime build to avoid conflicting with the normal toolchain runtime. They're really intended for very limited use - the intent being that you should be building your apps with the normal (gcc 11) toolchain and only using the gcc 8 compiler indirectly via nvcc for compiling If you really need to use an older toolchain globally, like we used to do with dunfell and earlier branches, you'll need to add in the recipes and configuration settings for that yourself. As for the package providing the gcc 8 version of |
Beta Was this translation helpful? Give feedback.
By libgcc1-8, are you talking about shared libraries for the gcc runtime? The gcc-for-nvcc recipes explicitly disable the shared runtime build to avoid conflicting with the normal toolchain runtime. They're really intended for very limited use - the intent being that you should be building your apps with the normal (gcc 11) toolchain and only using the gcc 8 compiler indirectly via nvcc for compiling
.cu
files.If you really need to use an older toolchain globally, like we used to do with dunfell and earlier branches, you'll need to add in the recipes and configuration settings for that yourself.
As for the package providing the gcc 8 version of
cc1
, runningoe-pkgdata-util find-path "*/cc1"