On 8/29/2022 2:11 PM, Jan-Benedict Glaw wrote:
Hi Jeff!
On Sun, 2022-08-28 15:32:53 -0600, Jeff Law via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
On 8/28/2022 1:50 AM, Jan-Benedict Glaw wrote:
On Tue, 2021-09-21 16:25:19 +0200, Richard Biener via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
This makes defaults.h choose DWARF2_DEBUG if PREFERRED_DEBUGGING_TYPE
is not specified by the target and errors out if DWARF DWARF is not supported.
While I think the pdp11 bits arreved, the rest did not (yet). Just
checked my auto-builder logs. When building current HEAD as
../gcc/configure --prefix=... --enable-werror-always \
--enable-languages=all --disable-gcov \
--disable-shared --disable-threads --without-headers \
--target=...
make V=1 all-gcc
ALL of these targets won't build right now:
[...]
Umm, most of those -elf targets do build. See:
http://law-sandy.freeddns.org:8080
Another builder. :) Randomly picking xtensa-elf, you're configuring
as
+ ../../gcc/configure --disable-analyzer --with-system-libunwind
--with-newlib --without-headers --disable-threads --disable-shared
--enable-languages=c,c++
--prefix=/home/jlaw/jenkins/workspace/xtensa-elf/xtensa-elf-obj/gcc/../../xtensa-elf-installed
--target=xtensa-elf
I guess the main difference that lets my builds fail might be
--enable-languages=all (vs. c,c++ in your case.)
Maybe you'd give that a try? (...and I'll trigger a build with just
c,c++ on my builder.)
I can, particularly now that the tester builds everything in a docker
container -- it really didn't like having Ada tests (for example)
appearing and disappearing based on whether or not the host had an Ada
compiler installed. I've also brought the computing resources in-house
(literally, in my house), so I'm not worried about running out of Amazon
credits anymore.
Jeff
