public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/31628] [gdb/testsuite] Support different compiler versions for different languages Date: Fri, 08 Nov 2024 08:08:32 +0000 [thread overview] Message-ID: <bug-31628-4717-onV8oY4zhm@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31628-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31628 --- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> --- I ran into this again. For some reason, on an aarch64-linux laptop with debian testing I got gcc 14 and ada 13 and ran into a failure in gdb.ada/scalar_storage.exp which checks gcc_major_version: ... if {[gcc_major_version] < 14} { ... Using gnatmake_version_at_least instead fixes this: ... if { ![gnatmake_version_at_least 14] } { ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-11-08 8:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-10 16:11 [Bug testsuite/31628] New: " vries at gcc dot gnu.org 2024-04-10 16:17 ` [Bug testsuite/31628] " vries at gcc dot gnu.org 2024-04-11 7:03 ` vries at gcc dot gnu.org 2024-11-08 8:08 ` vries at gcc dot gnu.org [this message] 2025-01-08 15:27 ` vries at gcc dot gnu.org
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=bug-31628-4717-onV8oY4zhm@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).