public inbox for
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <>
Subject: [Bug libdw/30077] Duplicate definition of typedef struct debuginfod_client in libdwfl
Date: Sun, 05 Feb 2023 10:46:21 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #5 from Mark Wielaard <mark at klomp dot org> ---
(In reply to David Edelsohn from comment #3)
> The struct is needed by libdwfl.h to prototype
> extern debuginfod_client *dwfl_get_debuginfod_client (Dwfl *dwfl);
> but that function is defined in debuginfod-client.c protected by
> It already is protected where it is referenced by an existing macro.  The
> problem is the header logic doesn't match the logic in the file that uses
> that prototype.
> So, again, it would seem better to include the struct from
> debuginfod-client.h directly instead of adding more macros to protect the
> headers and types that already are protected.  Something like:

The public headers are independent and can be used with or without the other
being available. And the function must be defined with or without libdebuginfod
support available or installed.

You cannot use the same guards in the public headers and the implementation
sources because they are independent.

It might be helpful to know in which configuration you are having this issue.

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

  parent reply	other threads:[~2023-02-05 10:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 20:12 [Bug libdw/30077] New: " dje at sourceware dot org
2023-02-04 17:32 ` [Bug libdw/30077] " mark at klomp dot org
2023-02-04 18:25 ` sam at gentoo dot org
2023-02-04 22:04 ` dje at sourceware dot org
2023-02-05 10:35 ` mark at klomp dot org
2023-02-05 10:46 ` mark at klomp dot org [this message]
2023-02-05 21:41 ` dje at sourceware dot org
2023-02-06  9:47 ` mark at klomp dot 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).