public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "dcantrell at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28783] New: Include libgen.h in tools/abisym.cc to support non-glibc systems
Date: Fri, 14 Jan 2022 17:08:10 +0000	[thread overview]
Message-ID: <bug-28783-9487@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28783
           Summary: Include libgen.h in tools/abisym.cc to support
                    non-glibc systems
           Product: libabigail
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: dcantrell at redhat dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

Created attachment 13907
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13907&action=edit
0001-Include-libgen.h-in-tools-abisym.cc-for-basename-3.patch

Ran in to this building and using libabigail on Alpine Linux, which is a
musl-based distribution.

I included libgen.h to pick up the basename(3) definition.  Musl provides the
POSIX basename(3) and not the GNU variant, but the usage in abisym.cc seems to
be within the scope of the POSIX basename(3).

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

             reply	other threads:[~2022-01-14 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 17:08 dcantrell at redhat dot com [this message]
2022-01-17 13:34 ` Dodji Seketeli
2022-01-17 13:34 ` [Bug default/28783] " dodji at seketeli dot org
2022-01-17 13:34 ` dodji 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-28783-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).