[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#28665: Testsuite summary for GNU sed 4.4 on Debian 8.8 PowerPC fails

From: Assaf Gordon
Subject: bug#28665: Testsuite summary for GNU sed 4.4 on Debian 8.8 PowerPC fails in 19 cases
Date: Mon, 2 Oct 2017 01:17:21 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0

Hello Dennis,

On 2017-10-01 05:06 PM, Dennis Clarke wrote:
> In almost every case the test log claims the test binary can not be found!
> deb8_ppc64$ file sed/sed
> sed/sed: ELF 64-bit MSB executable, 64-bit PowerPC or cisco 7500,
> version 1 (SYSV), dynamically linked, interpreter /lib64/ld64.so.1, for

Thank you for reporting this, with ample details.

Soon after the official release of sed-4.4 the test infrastructure
has been completely rewritten (and some outdated tests have been removed).

To help us understand if this is a current issue in 'sed'
or a problem in the tests,
may I ask you to try the latest development 'sed' version ?

If you can build from git (and have tools such as autotools/autoconf
installed), the commands would be:

    git clone git://git.sv.gnu.org/sed.git
    cd sed
    make check

Or, build for the latest development snapshot:


   tar -xf sed-4.4.84-a59fb.tar.xz
   cd sed-4.4.84-a59fb/
   make check

Please note this is not an official gpg-signed release
but a development snapshot. its sha1sum is:

   $ sha1sum sed-4.4.84-a59fb.tar.xz
   73a7428ba9cf84e1c89289dcd41de0a13ef6144f  sed-4.4.84-a59fb.tar.xz


If some tests still fail in this latest version, please attach the test
suite log file.

Can you also show the output of 'uname -a', which compiler are you using
(e.g. 'gcc -v'), and are you cross-compiling or building on the ppc64
machine directly ?

I've just tested the latest snapshop on gcc-compile-farm's ppc64 machine
(running centos 7), and there were no test failures.

 - assaf

This also relates to your other report (bug#28666 , binary3 test hangs),
I'll wait until we have more details before replying to it.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]