From: Immolo <immoloism@googlemail.com>
To: elfutils-devel@sourceware.org
Subject: elfutils-0.187 failing to build for a MUSL MIPS target
Date: Wed, 29 Jun 2022 11:18:43 +0000 [thread overview]
Message-ID: <CAHfWF5kxvZNS6F21JVQKqTMUec7A923aF4EunHDT4k8xV4SU-Q@mail.gmail.com> (raw)
Hi,
When trying to cross compile elfutils-0.187 for a MIPS device it fails with
various errors depending on the USE flags set on my crossdev Gentoo setup.
I believe but have not confirmed this is a MIPS issue until I have done
further tests.
in the MUSL overlay also fails with the same issue so I need to run some
further tests on other arches.
With USE="bzip2 nls threads utils" I get a numbe of undefined variables
with the final error "being undefined reference to `assert_perror'"
With USE="-*" then it becomes:
213 | if (fnmatch (pattern->pattern, name, FNM_EXTMATCH) == 0)
| ^~~~~~~~~~~~
| FNM_NOMATCH
/usr/mipsr5900el-unknown-linux-musl/tmp/portage/dev-libs/elfutils-0.187/work/elfutils-0.187/src/strip.c:213:44:
note: each undeclared identifier is reported only once for each
function it appears in
/usr/mipsr5900el-unknown-linux-musl/tmp/portage/dev-libs/elfutils-0.187/work/elfutils-0.187/src/strip.c:
In function ‘parse_opt’:
/usr/mipsr5900el-unknown-linux-musl/tmp/portage/dev-libs/elfutils-0.187/work/elfutils-0.187/src/strip.c:329:37:
error: ‘FNM_EXTMATCH’ undeclared (first use in this function); did you
mean ‘FNM_NOMATCH’?
329 | if (fnmatch (arg, ".comment", FNM_EXTMATCH) == 0)
| ^~~~~~~~~~~~
| FNM_NOMATCH
fI'll include the build logs for both below but I would be grateful if
anyone has any ideas on how I can start to solve this isse.
https://www.immolo.co.uk/elfutils/nouse-build.log
https://www.immolo.co.uk/elfutils/withuse-build.log
reply other threads:[~2022-06-29 11:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHfWF5kxvZNS6F21JVQKqTMUec7A923aF4EunHDT4k8xV4SU-Q@mail.gmail.com \
--to=immoloism@googlemail.com \
--cc=elfutils-devel@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).