Not reliably, because the GCC build system is quite monolithic and fragile.

The quickest way to get the libgcc's built is to configure and build with something like the following:

../gcc-src/configure --target=$TARGET --enable-languages=c
make all-target-libgcc
make install-target-libgcc

You might have to make all-gcc first, not sure if the dependencies are set up correctly.

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, running oe-pkgdata-util find-path "*/cc1" shows it's the cpp-8 package that provides it. And for on-target development, you can install the libgcc-8-dev package for the static libgcc-8 runtime support libraries.