Specific GCC version per package basis

[ZekeMorrin]

Hello, how can I *properly* set package.env to use a specific version of gcc to compile a package? Without encountering linking issues etc..

I have both GCC 14 and 13 installed, I want to use GCC-13 for compiling cuda and opencv related packages, that includes;

media-libs/opencv
dev-util/nvidia-cuda-toolkit
sci-libs/caffe2

I couldn't find the correct solution in older posts.

Thanks!

[leonik375]

Did you try this?
viewtopic-p-7996118.html#7996118

[grknight]

Beware of errors stemming from C++ library mismatches if this is attempted.

[oneone]

I cannot answer your question as to how to do this properly with absolute certainty, but here is what I did in order to compile hyprland with gcc-14 and the rest of my system with my default compiler gcc-13.

File /etc/portage/env/compiler-gcc-14:

Code: Select all

# Normal settings here
COMMON_FLAGS="-O2 -march=native"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"

CC="gcc-14"
CPP="g++-14" # necessary for xorg-server and possibly other packages
CXX="g++-14"

File /etc/portage/package.env/hypr.env:

Code: Select all

dev-libs/hyprgraphics compiler-gcc-14
gui-libs/hyprland-qtutils compiler-gcc-14
gui-wm/hyprland compiler-gcc-14
gui-libs/hyprutils compiler-gcc-14
gui-libs/aquamarine compiler-gcc-14
dev-cpp/tomlplusplus compiler-gcc-14
gui-apps/hypridle compiler-gcc-14
gui-apps/hyprlock compiler-gcc-14
gui-apps/hyprpaper compiler-gcc-14
gui-libs/hyprcursor compiler-gcc-14
dev-libs/hyprlang compiler-gcc-14
dev-libs/hyprland-protocols compiler-gcc-14
dev-util/hyprwayland-scanner compiler-gcc-14

But in fact I would prefer not having to do this, but I am in kind of a dilemma: Since gcc-14 is still unstable, I don't want to compile my whole system with it. On the other hand, hyprland requires gcc-14 (for spurious reasons in my opinion). See: https://github.com/hyprwm/Hyprland/issues/7508

I don't think there is a way to do this properly, because it probably shouldn't be done at all, but if anybody has any suggestions as to how to do this better, I would also appreciate their opinion.

[Hu]

gcc-14 looks stable to me.

Code: Select all

$ git log -1 --pretty=%H' %ad'
64a22966158c5c78b0a350ca573ff7386b6d687c Tue Jan 28 17:10:37 2025 +0800
$ git grep KEYWORDS -- sys-devel/gcc/gcc-14.*
sys-devel/gcc/gcc-14.2.1_p20241221.ebuild:30:   KEYWORDS="~alpha amd64 arm arm64 hppa ~loong ~mips ppc ppc64 ~riscv ~s390 sparc x86"

There are some keyword-masked newer versions, but the one shown is stable for the major platforms.

[freke]

Testing/mainly using gcc15 I've been using this for my /etc/portage/env/gcc14 for those packages that didn't yet play nice with gcc15

Code: Select all

PATH="/usr/x86_64-pc-linux-gnu/gcc-bin/14:${PATH}"
CC="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc"
CXX="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-g++"
AR="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc-ar"
NM="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc-nm"
RANLIB="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc-ranlib"

Can't remember where - but found that somewhere on the forums here.

[sam_]

Testing/mainly using gcc15 I've been using this for my /etc/portage/env/gcc14 for those packages that didn't yet play nice with gcc15

Code: Select all

PATH="/usr/x86_64-pc-linux-gnu/gcc-bin/14:${PATH}"
CC="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc"
CXX="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-g++"
AR="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc-ar"
NM="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc-nm"
RANLIB="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc-ranlib"

Can't remember where - but found that somewhere on the forums here.

You should really use workarounds wherever possible instead (like passing a particular flag as a workaround). You're free to ask me if you need help doing that.

Anyway, you don't need to do that -- you can do CC=x86_64-pc-linux-gnu-gcc-14 and so on instead.

[freke]

Testing/mainly using gcc15 I've been using this for my /etc/portage/env/gcc14 for those packages that didn't yet play nice with gcc15

Code: Select all

PATH="/usr/x86_64-pc-linux-gnu/gcc-bin/14:${PATH}"
CC="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc"
CXX="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-g++"
AR="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc-ar"
NM="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc-nm"
RANLIB="/usr/x86_64-pc-linux-gnu/gcc-bin/14/x86_64-pc-linux-gnu-gcc-ranlib"

Can't remember where - but found that somewhere on the forums here.

You should really use workarounds wherever possible instead (like passing a particular flag as a workaround). You're free to ask me if you need help doing that.

Anyway, you don't need to do that -- you can do CC=x86_64-pc-linux-gnu-gcc-14 and so on instead.

Thanks - I currently don't have any packages using my gcc14-env, though

I'm passing -std=gnu17 to three packages

Code: Select all

## c23-porting
=dev-perl/Bit-Vector-7.400.0-r3 porting
=net-mail/dovecot-2.3.21.1-r1 porting
=net-misc/iperf-3.17.1 porting

[ZekeMorrin]

Thanks for all the good replies, these will be useful for me. And I second to that gcc-14 is pretty stable now, it's not even keyworded anymore. (~amd64)

I'll do it as @oneone did it;

CC="gcc-14"
CPP="g++-14" # necessary for xorg-server and possibly other packages
CXX="g++-14"

but gcc-13 instead.

cuda package has hard dependency for gcc-13 but I'm not sure if it's using the compiler to install the package or just the libraries.

[oneone]

Thanks for all the answers as well. I was not aware that gcc did become stable since the last time I checked. Time for me to upgrade