From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Always default to DWARF2_DEBUG if not specified, warn about deprecated STABS
Date: Mon, 29 Aug 2022 22:11:35 +0200 [thread overview]
Message-ID: <20220829201135.xubk4zklljx7eaog@lug-owl.de> (raw)
In-Reply-To: <1a195efa-f8f0-61b0-71b8-8d566fa5e9c2@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
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.)
MfG, JBG
--
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-08-29 20:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 14:25 Richard Biener
2021-09-28 6:14 ` Richard Biener
2021-09-28 13:18 ` Koning, Paul
2021-10-15 8:23 ` Richard Biener
2021-10-23 20:00 ` Jan-Benedict Glaw
2021-10-23 22:19 ` Jeff Law
2021-10-24 6:36 ` Richard Biener
2021-10-24 7:20 ` Jan-Benedict Glaw
2021-10-25 8:25 ` Richard Biener
2021-10-26 1:28 ` Joseph Myers
2021-10-29 14:48 ` ibuclaw
2022-08-28 7:50 ` Jan-Benedict Glaw
2022-08-28 21:32 ` Jeff Law
2022-08-29 20:11 ` Jan-Benedict Glaw [this message]
2022-08-31 16:05 ` Jeff Law
2022-09-07 10:50 ` Jan-Benedict Glaw
2022-09-07 11:57 ` Richard Biener
-- strict thread matches above, loose matches on Subject: below --
2021-09-10 12:12 Richard Biener
2021-09-10 15:08 ` Michael Matz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220829201135.xubk4zklljx7eaog@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).