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 build/30295] Undefined reference for gcore_elf_make_tdesc_note in linux-tdep with slibtool
Date: Wed, 21 Feb 2024 00:54:55 +0000	[thread overview]
Message-ID: <bug-30295-4717-CYPD8EOzgb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30295-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30295

--- Comment #10 from orbea <orbea at riseup dot net> ---
> From what I can see, there's no real reason for GDB_AC_CHECK_BFD
> to be doing a link check at all.
> I wonder if changing this to do a compile check would help.

This seems like a good idea, but when I tried it it results in undefined
references to 'bfd_mach_o_lookup_command' since both the ELF and MACH-O tests
now pass.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-02-21  0:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  6:04 [Bug compile/30295] New: " orbea at riseup dot net
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 [this message]
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-CYPD8EOzgb@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).