On Tue, Jun 13, 2023 at 6:35 AM Randy Galbraith <randy.galbraith@xxxxxxxxx> wrote: > > > On Tue, Jun 13, 2023 at 3:43 AM Christer Solskogen via Gcc-help < > gcc-help@xxxxxxxxxxx> wrote: > >> On 12.06.2023 17:54, Randy Galbraith via Gcc-help wrote: >> >> > Hi Jonathan. Even though using GCC 13 may not work for us, I decided to >> > test the build of gcc-13.1.0 (with gmp-6.2.1, mpfr-4.2.0 and mpc-1.3.1): >> > >> > ./configure --enable-languages=c,c++ >> > make >> > >> > Alas it seems to run into the same issue wherein ./conftest runs forever >> > (>1hr, 40min, with 32:22 of cpu time). I'm now going to try export >> CC=xlc >> > and see if I can get gcc 5.4.0 to build. Cheers, -Randy >> > >> >> Don't build gcc from the source directory. This is not supported. >> https://gcc.gnu.org/wiki/InstallingGCC >> >> -- >> chs >> >> Interesting! I watched a Youtube video wherein an individual built GCC > (14.0 actually) from git repo. He stepped outside the source directory, but > I assumed he was just wanting to avoid building right where .git exists. > I'm being tripped up by the learned habit of ./configure && make used by > many packages. Thanks for the wiki link. Cheers, -Randy > Quick reply to drop off this note. Running make outside the gcc source directory (objdir, as per following the wiki) did not help here. Nonetheless the step: ./contrib/download_prerequisites did show what GCC 5.4.0 wants in terms of gmp, mpfr, mpc and isl). I'm now going to run some of the build steps we use to compile our own software. That may reveal ld (or CFLAGS) options that are needed to make g++ and ld agree upon object code. Cheers, -Randy
