[Bug bootstrap/106472] No rule to make target '../libbacktrace/libbacktrace.la', needed by 'libgo.la'.

2022-09-19 Thread jeffrey.rahr at baesystems dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472

--- Comment #21 from Jeff Rahr  ---
Roger - I was getting that same error when building out of the box for
langueages=c,c++,fortran,lto,jit,go,d (ie didn't edit Makefile.def). Based on
https://forum.dlang.org/post/qgrchukzyceflenrr...@forum.dlang.org that said on
some platforms libphobos is not enabled by default,  I added --enable-libphobos
to my configure and my build worked after that.

[Bug bootstrap/106472] No rule to make target '../libbacktrace/libbacktrace.la', needed by 'libgo.la'.

2022-09-19 Thread jeffrey.rahr at baesystems dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472

--- Comment #19 from Jeff Rahr  ---
I added D language to my build and was able to get 12.2 to build "out of the
box" without editing Makefile.def on x86-64-pc-linux-gnu. Make is using 4
processors.

[Bug bootstrap/106472] No rule to make target '../libbacktrace/libbacktrace.la', needed by 'libgo.la'.

2022-09-14 Thread jeffrey.rahr at baesystems dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472

--- Comment #18 from Jeff Rahr  ---
Thomas - After applying this patch, I reran 'autogen Makefile.def' so that line
was already in Makefile.in. I am able to get gcc to build if I remove the
bootstrap=true from libbacktrace and libatomic on lines 172 and 194 in
Makefile.def. This was added to Makefile.def as part of a patch to D language
by:
https://github.com/gcc-mirror/gcc/commit/5fee5ec362f7a243f459e6378fd49dfc89dc9fb5

I am not building D language, so not sure if I was building D it would make any
difference.

[Bug bootstrap/106472] No rule to make target '../libbacktrace/libbacktrace.la', needed by 'libgo.la'.

2022-08-12 Thread jeffrey.rahr at baesystems dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472

Jeff Rahr  changed:

   What|Removed |Added

 CC||jeffrey.rahr at baesystems dot 
com

--- Comment #15 from Jeff Rahr  ---
I am still seeing this issue after the patch as well.