From: David Bremner <david@tethera.net>
To: "Dan Čermák" <dan.cermak@posteo.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Last call for NEWS entries for 0.31
Date: Mon, 07 Sep 2020 08:23:32 -0300 [thread overview]
Message-ID: <87eendu8y3.fsf@tethera.net> (raw)
In-Reply-To: <87363uhvxq.fsf@cgc-instruments.com>
Dan Čermák <dan.cermak@posteo.net> writes:
> David Bremner <david@tethera.net> writes:
>
>> Dan Čermák <dan.cermak@posteo.net> writes:
>>
>>> - on ppc64 "comparing existing to exported symbols" from
>>> T360-symbol-hiding fails as well
>>
>> This is more-or-less known [1]. The problem is that ppc64 reports
>> defined functions as 'D' in nm output. At least on ELF architectures,
>> readelf -Ws is more reliable. How many people would using readelf break
>> things for? Currently the test does not run on macOS, afaik.
>
> So it is ok if I just skip this test on ppc64? Or can anything be done
> about this (I must admit that I have relatively little insight into
> this)?
I'd say it's OK to skip it for now. Hopefully we will fix it for the
next release; I didn't want to make the switch to readelf in the late
stages of a release.
d
next prev parent reply other threads:[~2020-09-07 11:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 15:16 starting release process for 0.31 David Bremner
2020-08-18 11:27 ` David Bremner
2020-08-18 11:45 ` David Bremner
2020-08-22 13:04 ` call for NEWS entries " David Bremner
2020-08-29 12:27 ` Last " David Bremner
2020-08-30 11:34 ` David Bremner
2020-09-01 8:13 ` Dan Čermák
2020-09-01 13:19 ` David Bremner
2020-09-07 7:42 ` Dan Čermák
2020-09-07 7:45 ` Dan Čermák
2020-09-07 11:23 ` David Bremner [this message]
2020-09-08 7:53 ` Dan Čermák
2020-09-08 11:52 ` test failures on ppc64 David Bremner
2020-09-04 10:21 ` call for NEWS entries for 0.31 Mark Walters
2020-09-04 10:59 ` David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eendu8y3.fsf@tethera.net \
--to=david@tethera.net \
--cc=dan.cermak@posteo.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).