From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mahalingam Kanagasabapathy <mahalingam.k@embedur.com>
Cc: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: elfutils configuration issue on musl
Date: Mon, 11 Jul 2022 09:19:47 -0400 [thread overview]
Message-ID: <20220711131947.GA11328@redhat.com> (raw)
In-Reply-To: <DM6PR15MB26500E348E3AC6398D7B2CA299879@DM6PR15MB2650.namprd15.prod.outlook.com>
Hi -
> I am working on building elfutils for a project where I am building for i3x86 with musl and I am facing configure: WARNING: "libc does not have argp"
> checking for argp_parse in -largp... no
> configure: error: "no libargp found"
Yes, musl does not include an implementation of the argp API.
This is brought up with musl folks regularly. This may help:
https://www.openwall.com/lists/musl/2019/01/06/2
- FChE
next prev parent reply other threads:[~2022-07-11 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 9:42 Mahalingam Kanagasabapathy
2022-07-11 13:19 ` Frank Ch. Eigler [this message]
2022-07-12 9:17 ` Mahalingam Kanagasabapathy
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=20220711131947.GA11328@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=mahalingam.k@embedur.com \
/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).