public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "orbea at riseup dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug compile/30295] New: Undefined reference for gcore_elf_make_tdesc_note in linux-tdep with slibtool
Date: Fri, 31 Mar 2023 06:04:58 +0000 [thread overview]
Message-ID: <bug-30295-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30295
Bug ID: 30295
Summary: Undefined reference for gcore_elf_make_tdesc_note in
linux-tdep with slibtool
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: compile
Assignee: unassigned at sourceware dot org
Reporter: orbea at riseup dot net
Target Milestone: ---
Created attachment 14792
--> https://sourceware.org/bugzilla/attachment.cgi?id=14792&action=edit
Build fix patch
When building with slibtool there is an undefined reference for
'gcore_elf_make_tdesc_note' in linux-tdep.c. This can be solved by moving
gcore-elf.c to the same COMMON_SFILES variable as is gcore.c which is already
the same in the HFILES_NO_SRCDIR variable for the gcore-elf.h and gcore.h
header files.
I attached a patch showing a potential fix.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-03-31 6:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 6:04 orbea at riseup dot net [this message]
2023-03-31 6:06 ` [Bug compile/30295] " orbea at riseup dot net
2023-03-31 14:05 ` [Bug build/30295] " tromey at sourceware dot org
2023-03-31 14:17 ` tromey at sourceware dot org
2023-03-31 15:42 ` orbea at riseup dot net
2023-03-31 17:15 ` orbea at riseup dot net
2023-04-21 18:16 ` orbea at riseup dot net
2023-08-28 13:53 ` tromey at sourceware dot org
2024-02-16 17:20 ` tromey at sourceware dot org
2024-02-16 17:29 ` orbea at riseup dot net
2024-02-20 18:14 ` tromey at sourceware dot org
2024-02-21 0:54 ` orbea at riseup dot net
2024-04-07 18:33 ` orbea at riseup dot net
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-30295-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).