Open necrose99 opened 1 year ago
I believe I am tracking your ask here. Could you please provide an example of how you are using this? The original intent of gcc-config is to help rebuild the tool chain if upgrades are needed. Would be nice to patch this to support both use cases here. Thanks
USE="clang" emerge genup
{else gcc-config will default .. }
deps: for symlinks / replaces gcc-config in this case.. with these symlink package ie replace binutils/gcc linker to clang equivs.. sys-devel/llvm-toolchain-symlinks
sys-devel/clang-toolchain-symlinks
sys-devel/lld-toolchain-symlinks
blocks sys-devel/gcc-config
for amd64 / etc you can use pure clang and gcc is symlinked against clang ...
with USE/make.conf Arm64 etc for cross-compilation on llvm is also very doable... package.use/sys-devel/llvm-clang
also bug on gentoo to do CHost automagics per target as improvements so not needing crossdev's fun irritations
to force GCC for some packages / etc env/fallback wiki below.. https://wiki.gentoo.org/wiki/Clang#GCC_fallback_environment
Thanks for the clarifications. genup is EOL, this fork incorporates changes needed to be useful to me. That being said, I understand the need here yet this feature will be low on my priority lists. PR's are welcome :smiley: It sounds like this will need a new "USE_CLANG" boolean in the script to incorporate this.
gcc-config can be doped in favor of clag gcc symlinks packages...
hover genup will gripe if you do...