On Tue, 21 May 2019 at 20:35, flandraco <dirk.seynhaeve@xxxxxxxxx> wrote: > > A year late and happy with the solution suggested by @Jonathan Wakely. > > However I need to note that the "official" instructions are if not > conflicting with Jonathan's advice, then at least they are very ambiguous: > https://gcc.gnu.org/install/download.html > Seems to indicate that binutils should be installed with the in-tree method > indeed? It says "If you also intend to build binutils ..." That doesn't say it *should* be done like that. But it might help to mention that the in-tree method has caveats. > *Who can update those official notes with the "working" method?* Anybody can send a patch for the docs: https://gcc.gnu.org/contribute.html#docchanges The source for that file is: https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/doc/install.texi;h=e5a7d83bfd29477a81df1b06199d4facc09132e0;hb=HEAD > As I build a variety of toolchains, I have established the following > "working" combinations (similar to what @Matt Godbolt is suggesting): > # GCC => Binutils > # 9.1.0: May.03/2019 => Feb.02/2019 : 2.32 > # 8.3.0: Feb.22/2019 => Feb.02/2019 : 2.32 > # 8.2.0: Jul.26/2018 => Jul.18/2018 : 2.31.1 > # 8.1.0: May.02/2018 => Jan.28/2018 : 2.30 > # 7.4.0: Dec.06/2018 => Jul.18/2018 : 2.31.1 > # 7.3.0: Jan.25/2018 => Sep.25/2017 : 2.29.1 > # 7.2.0: Aug.14/2017 => Jul.25/2017 : 2.28.1 > # 7.1.0: May.02/2017 => Mar.02/2017 : 2.28 > # 6.5.0: Oct.26/2018 => Jul.18/2016 : 2.31 > # 6.4.0: Jul.04/2017 => Mar.02/2017 : 2.28 > # 6.3.0: Dec.21/2016 => Aug.03/2016 : 2.27 > # 5.5.0: Oct.10/2017 => Sep.25/2017 : 2.29 > # 5.4.0: Jun.03/2016 => Jan.25/2016 : 2.26 > > Since this is based on pure dates, and not on actual branches: > *Where can I find the "correct" combination? GCC and binutils are maintained in separate repositories, so there are no "actual branches" in common. If you want more than dates then you'd have to inspect the repo histories to see when the top-level configure files were synced between the two repos.
