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] New: 32-bit build failure with --enable-targets=all
Date: Wed, 04 May 2022 07:58:57 +0000 [thread overview]
Message-ID: <bug-29119-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29119
Bug ID: 29119
Summary: 32-bit build failure with --enable-targets=all
Product: gdb
Version: 12.1
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: luis.machado at arm dot com
CC: tromey at sourceware dot org
Target Milestone: ---
Host: *-linux-gnu
Target: *
Build: *-linux-gnu
Currently, a 32-bit build of binutils-gdb on Linux doesn't complete if we pass
the --enable-targets=all switch. There are a few problems in the list of files
included for 32-bit bfd and 64-bit bfd.
This ticket aims to track these fixes so we can backport them to GDB 12.1.
>From the top of my head, we have the following:
1 - [opcodes] Move TILE-Gx files from TARGET32_LIBOPCODES_CFILES to
TARGET64_LIBOPCODES_CFILES
(https://sourceware.org/pipermail/binutils/2022-May/120651.html).
2 - [gdb] Move bpf, tile-gx and loongarch files from ALL_TARGET_OBS to
ALL_64_TARGET_OBS
(https://sourceware.org/pipermail/gdb-patches/2022-May/188650.html).
3 - [opcodes] Don't define ARCH_cris for 64-bit BFD, since it is a 32-bit
architecture (https://sourceware.org/pipermail/binutils/2022-May/120662.html).
4 - [sim] There is fallout from moving cris to the 32-bit bfd list that needs
to be addressed in the print formatters.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-05-04 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 7:58 luis.machado at arm dot com [this message]
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
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@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: 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).