Ühel kenal päeval, E, 15.04.2019 kell 10:40, kirjutas allan gottlieb: > On one of my machines I see > > gottlieb@E6430 ~ $ eselect binutils list > [1] x86_64-pc-linux-gnu-2.28.1 * > [2] x86_64-pc-linux-gnu-2.29.1 > [3] x86_64-pc-linux-gnu-2.30 > [4] x86_64-pc-linux-gnu-2.31.1 > > But I also see > > gottlieb@E6430 ~ $ eix -I -e binutils > [?] sys-devel/binutils > ... > (2.28.1) [M]2.28.1 > (2.29.1) [M]2.29.1-r1 > (2.30) 2.30-r4 > (2.31) 2.31.1-r4 ~2.31.1-r5 > ... > > So I am using a masked version of binutils, which seems bad. > > I presume I should do > eselect binutils set 4 > > I am asking for confirmation since I realize breaking binutils > is not fun.
Yes, you should be using a newer version. I suggest reviewing your gcc- config as well; changing that may involve some migration (especially if very old version by now) or some specific rebuild needs. But binutils is generally an easy fire and forget switchover. After a bigger binutils or gcc upgrade (typically different major.minor) you should usually actually switch to it as well, and if everything worked out good, you can depclean the older versions (or keep 1-2 around for safety; or more if you actually need to test older GCC for some own programming work). Best, Mart
signature.asc
Description: This is a digitally signed message part
