From: Assaf Gordon <assafgordon@gmail.com>
To: Gopinath Sekar <Gopinath.Sekar@contactenergy.co.nz>,
39652@debbugs.gnu.org,
"bug-gnulib@gnu.org List" <bug-gnulib@gnu.org>
Subject: Re: bug#39652: SED preinstall check failed
Date: Wed, 19 Feb 2020 22:35:08 -0700 [thread overview]
Message-ID: <6fa966a6-0463-425e-a316-815f630f9130@gmail.com> (raw)
In-Reply-To: <MEAPR01MB2854E5BD7320A35AE77BC677C2110@MEAPR01MB2854.ausprd01.prod.outlook.com>
tag 39652 moreinfo
stop
(added bug-gnulib@)
Hello,
On 2020-02-17 8:12 p.m., Gopinath Sekar via wrote:
> FAIL: test-rename
[...]
> ============================================================================
> See gnulib-tests/test-suite.log
> Please report to bug-sed@gnu.org
> ============================================================================
> Makefile:3038: recipe for target 'test-suite.log' failed
> make[6]: *** [test-suite.log] Error 1
> make[6]: Leaving directory '/home/sekar/sed-4.4/gnulib-tests'
Thank you for the report.
This failure is not in sed directly, but a library called "gnulib"
(which GNU sed uses).
I've added the gnulib mailing list to this discussion.
To help us diagnose the issue, please attach the log file
( gnulib-tests/test-suite.log ), and the details of your system
(e.g. "uname -a" and "gcc --version" and "df -T").
Additionally, sed version 4.4 is three years old.
If possible, please test with the latest sed version 4.8.
regards,
- assaf
parent reply other threads:[~2020-02-20 5:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <MEAPR01MB2854E5BD7320A35AE77BC677C2110@MEAPR01MB2854.ausprd01.prod.outlook.com>]
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6fa966a6-0463-425e-a316-815f630f9130@gmail.com \
--to=assafgordon@gmail.com \
--cc=39652@debbugs.gnu.org \
--cc=Gopinath.Sekar@contactenergy.co.nz \
--cc=bug-gnulib@gnu.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).