public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26565] New: Support specifying --header-dir{1,2} several times on the command line of abidiff
Date: Wed, 02 Sep 2020 06:50:37 +0000	[thread overview]
Message-ID: <bug-26565-9487@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26565
           Summary: Support specifying --header-dir{1,2} several times on
                    the command line of abidiff
           Product: libabigail
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: dodji at redhat dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

Sometimes, a binary (shared binary for instance) might come with its header
files spread over several directories.  In that case we must be able to let
abidiff know about all the header files directories by specifying the
--headers-dir1 (or --headers-dir2) several times on the command line, just like
what can be done with --debug-info-dir{1,2}.

The same thing must be supported for the --headers-dir option of abidw.

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

             reply	other threads:[~2020-09-02  6:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  6:50 dodji at redhat dot com [this message]
2020-09-02  6:51 ` [Bug default/26565] " dodji at redhat dot com
2020-09-02  7:03 ` dodji at redhat dot com
2020-09-18 14:39 ` dodji at redhat dot com
2020-09-18 15:09 ` dcantrell at redhat 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-26565-9487@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libabigail@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).