public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Tom Tromey <tom@tromey.com>, gdb-testers@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): binutils-gdb - failed compile (failure) (master)
Date: Mon, 22 Apr 2024 07:12:02 -0600 [thread overview]
Message-ID: <871q6xfsnx.fsf@tromey.com> (raw)
In-Reply-To: <20240422080228.GA28568@gnu.wildebeest.org> (Mark Wielaard's message of "Mon, 22 Apr 2024 10:02:28 +0200")
>>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:
Mark> ../../binutils-gdb/gdb/c-exp.y: In function ‘void c_print_token(FILE*, int, c_exp_YYSTYPE)’:
Mark> ../../binutils-gdb/gdb/c-exp.y:3433:29: error: ‘val’ was not declared in this scope
Mark> value.tsval.length, val.tsval.ptr);
Mark> ^~~
Mark> ../../binutils-gdb/gdb/c-exp.y:3433:29: note: suggested alternative: ‘value’
Mark> value.tsval.length, val.tsval.ptr);
Mark> ^~~
Mark> value
Mark> make[1]: *** [Makefile:1950: c-exp.o] Error 1
Mark> val being value here looks correct, but I don't understand why it
Mark> isn't failing on all other arches.
Kévin noticed this as well.
I also don't understand why I didn't see this -- I've built this patch
at least a half dozen times, and regression-tested it.
Anyway I see Andrew already fixed it.
Tom
next prev parent reply other threads:[~2024-04-22 13:12 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 19:53 builder
2024-04-22 8:02 ` Mark Wielaard
2024-04-22 13:12 ` Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-02 18:19 builder
2024-04-03 15:00 builder
2024-03-25 22:35 builder
2024-03-25 20:31 builder
2024-03-25 20:27 builder
2024-01-29 19:39 builder
2024-01-22 20:26 builder
2024-01-16 7:36 builder
2024-01-16 7:04 builder
2024-01-15 20:47 builder
2023-12-29 9:19 builder
2023-12-08 4:54 builder
2023-11-24 9:05 builder
2023-11-22 2:13 builder
2023-11-22 1:06 builder
2023-10-06 20:20 builder
2023-09-25 14:20 builder
2023-09-25 9:35 builder
2023-09-25 8:56 builder
2023-08-25 20:10 builder
2023-08-21 17:29 builder
2023-08-19 7:17 builder
2023-08-18 17:49 builder
2023-08-11 7:43 builder
2023-08-02 9:36 builder
2023-07-21 11:58 builder
2023-06-05 17:50 builder
2023-05-26 9:07 builder
2023-05-23 20:15 builder
2023-05-16 9:50 builder
2023-05-12 20:21 builder
2023-05-05 17:39 builder
2023-05-02 16:24 builder
2023-05-01 20:08 builder
2023-05-01 5:55 builder
2023-04-29 7:07 builder
2023-04-28 17:35 builder
2023-04-27 13:27 builder
2023-04-27 0:36 builder
2023-04-26 17:35 builder
2023-04-26 6:13 builder
2023-04-24 20:24 builder
2023-04-24 14:38 builder
2023-04-24 0:29 builder
2023-04-21 14:02 builder
2023-04-21 3:59 builder
2023-04-14 21:36 builder
2023-04-13 20:24 builder
2023-04-07 0:28 builder
2023-04-06 0:46 builder
2023-04-03 14:09 builder
2023-03-30 22:05 builder
2023-03-28 22:47 builder
2023-03-27 15:38 builder
2023-03-23 7:56 builder
2023-03-22 21:46 builder
2023-03-20 8:45 builder
2023-03-18 21:44 builder
2023-03-18 19:15 builder
2023-03-15 18:42 builder
2023-03-10 16:23 builder
2023-03-07 10:45 builder
2023-03-06 0:28 builder
2023-02-28 12:34 builder
2023-02-28 12:13 builder
2023-02-27 15:15 builder
2023-02-25 10:45 builder
2023-02-24 20:13 builder
2023-02-20 22:05 builder
2023-02-17 1:11 builder
2023-02-14 19:22 builder
2023-02-14 6:07 builder
2023-02-14 1:50 builder
2023-02-11 3:21 builder
2023-02-09 19:26 builder
2023-02-09 0:59 builder
2023-01-30 20:40 builder
2023-01-26 16:42 builder
2023-01-25 13:05 builder
2023-01-23 20:34 builder
2023-01-19 0:23 builder
2023-01-17 14:32 builder
2023-01-17 11:48 builder
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=871q6xfsnx.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-testers@sourceware.org \
--cc=mark@klomp.org \
/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).