From: jose.marchesi@oracle.com (Jose E. Marchesi)
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: Prepare for elfutils 0.170
Date: Wed, 02 Aug 2017 19:21:00 -0000 [thread overview]
Message-ID: <873799wzbc.fsf@oracle.com> (raw)
In-Reply-To: <877eylwzuk.fsf@oracle.com> (Jose E. Marchesi's message of "Wed, 02 Aug 2017 21:09:55 +0200")
> It has been 3 months again so time for another update.
> I just pushed the version bump update and would like to do a release
> tomorrow unless some showstoppers are found.
I tested current git master on Debian 8 amd64, Debian 9 amd64, Fedora
rawhide x86_64, ppc64le, aarch64, ppc64, i686, s390x, armv7hl, RHEL6
ppc, s390, x86_64, ppc64, i686, s390x and RHEL7 ppc, x86_64, s390,
aarch64, ppc64le, ppc64, i686, s390x all with zero FAIL.
Tried to build latest master in sparc64:
../../src/readelf.c:3805:7: error: ‘DWARF_ALL_KNOWN_DW_DEFAULTED’
undeclared (first use in this function); did you mean ‘DWARF_ALL_KNOWN_DW_ATE’?
Seems like a typo in readelf.c:dwarf_defaulted_string:
#define DWARF_ONE_KNOWN_DW_DEFAULTED(NAME, CODE) [CODE] = #NAME,
DWARF_ALL_KNOWN_DW_DEFAULTED
#undef DWARF_ONE_KNOWN_DW_DEFAULTED
Never mind... now that I bothered to actually read what that code does,
found the problem was I didnt configure enabling maintainer mode...
Maybe it would be good to update libdw/known-dwarf.h in the git repo...
PS: all 172 tests passed in sparc64-linux-gnu
next prev parent reply other threads:[~2017-08-02 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 16:43 Mark Wielaard
2017-08-02 18:52 ` Mark Wielaard
2017-08-02 19:10 ` Jose E. Marchesi
2017-08-02 19:21 ` Jose E. Marchesi [this message]
2017-08-02 19:37 ` Mark Wielaard
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=873799wzbc.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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).