public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "luis.machado at arm dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29119] 32-bit build failure with --enable-targets=all Date: Thu, 16 Jun 2022 08:52:56 +0000 [thread overview] Message-ID: <bug-29119-4717-68lw4ohsP5@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29119-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29119 --- Comment #4 from Luis Machado <luis.machado at arm dot com> --- New commit related to this: commit 33b90f59f3465041a620ad4f6504a35b578cfc65 Author: Sergei Trofimovich <siarheit@google.com> Date: Sat May 21 08:53:50 2022 +0100 sim: fix BFD_VMA format arguments on 32-bit hosts [PR gdb/29184] Noticed format mismatch when attempted to build gdb on i686-linux-gnu in --enable-64-bit-bfd mode: sim/../../sim/cris/sim-if.c:576:28: error: format '%lx' expects argument of type 'long unsigned int', but argument 4 has type 'bfd_size_type' {aka 'long long unsigned int'} [-Werror=format=] 576 | sim_do_commandf (sd, "memory region 0x%" BFD_VMA_FMT "x,0x%lx", | ^~~~~~~~~~~~~~~~~~~ 577 | interp_load_addr, interpsiz); | ~~~~~~~~~ | | | bfd_size_type {aka long long unsigned int} While at it fixed format string for time-related types. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-16 8:52 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-04 7:58 [Bug gdb/29119] New: " luis.machado at arm dot com 2022-05-04 8:03 ` [Bug gdb/29119] " luis.machado at arm dot com 2022-05-05 9:13 ` luis.machado at arm dot com 2022-05-30 14:09 ` luis.machado at arm dot com 2022-06-05 23:26 ` sam at gentoo dot org 2022-06-16 8:52 ` luis.machado at arm dot com [this message] 2022-06-16 8:53 ` luis.machado at arm dot com 2022-06-16 9:15 ` luis.machado at arm dot com 2022-09-09 8:48 ` luis.machado at arm dot com
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-29119-4717-68lw4ohsP5@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).