public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Dodji Seketeli <dodji@seketeli.org>
To: David Seifert <soap@gentoo.org>
Cc: libabigail@sourceware.org
Subject: Re: [PATCH] Find fts-standalone on musl
Date: Mon, 07 Feb 2022 16:28:10 +0100	[thread overview]
Message-ID: <87a6f2n1bp.fsf@seketeli.org> (raw)
In-Reply-To: <20220207141759.1712914-1-soap@gentoo.org> (David Seifert's message of "Mon, 7 Feb 2022 15:17:59 +0100")

David Seifert <soap@gentoo.org> a écrit:

> From: Dodji Seketeli <dodji@seketeli.org>
>
> When using the musl C library fts is optional.  So we need to detect
> its presence by looking at the fts-standalone pkgconfig module.
>
> This patch does that.
>
> This comes from Gentoo bug https://bugs.gentoo.org/831571
>
> 	* configure.ac: Invoke AC_CANONICAL_HOST to compute the host_cpu,
> 	host_vendor, host_os parts of the 'host" variable.  Then if the
> 	host_os ends up with "musl" then, check for the fts-standalone
> 	pkgconfig module and record the fts library into
> 	FTS_{LIBS,CFLAGS}.
> 	* src/Makefile.am: Link to $FTS_LIBS and use $FTS_CFLAGS for
> 	compilation.
> 	* tools/Makefile.am: Likewise.
> 	* tools/abisym.cc: Include libgen.h
> 	* tools/kmidiff.cc: Remove useless fts.h header file.
>
> Signed-off-by: David Seifert <soap@gentoo.org>
> Signed-off-by: Dodji Seketeli <dodji@redhat.com>

Applied to master, thanks!

[...]

Cheers,

-- 
		Dodji

       reply	other threads:[~2022-02-07 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220207141759.1712914-1-soap@gentoo.org>
2022-02-07 15:28 ` Dodji Seketeli [this message]
2022-02-07 15:36   ` David Seifert
2022-01-29 19:31 David Seifert
2022-01-29 19:43 ` David Seifert
2022-02-07 14:13 ` Dodji Seketeli

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=87a6f2n1bp.fsf@seketeli.org \
    --to=dodji@seketeli.org \
    --cc=libabigail@sourceware.org \
    --cc=soap@gentoo.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).