This is why, additionally, it is nice to know whether version numbers for given software are meaningful, for example, are they following Semantic Versioning? That would give clear indication of how far to update. I see that page https://ftp.gnu.org/gnu/binutils lists releases since 1996, starting with version 2.6 ...25 years later, they continue with major version 2 ...that this mean that they are all backwards compatible? If that is the case, then, I should be able to use even binutils released after the version of gcc I am trying to use, correct? On Sun, Jun 27, 2021 at 4:58 PM NightStrike <nightstrike@xxxxxxxxx> wrote: > On Fri, Jun 25, 2021 at 10:59 AM Jonathan Wakely via Gcc-help > <gcc-help@xxxxxxxxxxx> wrote: > > > > On Fri, 25 Jun 2021 at 14:32, German Salazar wrote: > > > > > > Over time and because of different user requirements, I have ended up > with > > > 3 versions of gcc installed and, apparently, I use each with a specific > > > version of binutils. > > > > > > Memories are vague, I either found a table indicating which version > > > of binutils is needed by a given version of gcc or I found out the > hard way > > > while attempting to use gcc. > > > > > > Presently, I use > > > binutils 2.24 with gcc 4.9.2 > > > binutils 2.25 with gcc 5.3.0 > > > binutils 2.26 with gcc 6.3.0 > > > > > > I am about to install gcc 10.3.0 > > > *Question: which version of binutils should I use?* > > > I can't seem to find a hint about that, anywhere. > > > > It doesn't matter, anything made in the last ten years will work fine. > > Generally, the newer the better, because GCC can take advantage of the > > newer features. But it will still work without them. > > I have found that older binutils don't scale well with newer gcc once > you try doing anything but the basics, even on x86_64 / Linux. It's > largely why I kind of wish the projects were not separate. > > The same goes for gdb. You just can't use an old gdb with a new gcc > and expect things to work without using additional options to force > legacy behavior (and even then, sometimes it won't matter). > > This is why I've started making the entire toolchain, > gcc+binutils+gdb. Although, as you've seen in certain problems you've > tried to help me with, Jon, I fail at that, too, on occasion. >
