bug-m4
[Top][All Lists]
Advanced

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

RE: Test failure in GNU M4 1.4.18


From: Oppe, Thomas C ERDC-RDE-ITL-MS Contractor
Subject: RE: Test failure in GNU M4 1.4.18
Date: Fri, 6 Sep 2019 02:03:44 +0000

Eric,

First, I apologize for not providing more information about this test
failure report.

I am installing m4 in order to build and test the GCC 9.2.0 release on a
variety of Cray and HPE/SGI platforms available in the DoD HPCMP (High
Performance Computing Modernization Program) for the Army Corps of
Engineers.  Here are some platform details:

voodoo03> uname -a
Linux voodoo03 3.10.0-862.3.2.el7.x86_64 #1 SMP Tue May 15 18:22:15 EDT 2018
x86_64 x86_64 x86_64 GNU/Linux

voodoo03> uname -srv
Linux 3.10.0-862.3.2.el7.x86_64 #1 SMP Tue May 15 18:22:15 EDT 2018

The compiler is:

voodoo03> gcc --version
gcc (GCC) 6.3.0

************************************
File:  m4-1.4.18/tests/test-symlink.log
************************************

voodoo03> more m4-1.4.18/tests/test-symlink.log
test-symlink.h:70: assertion 'errno == EEXIST || errno == EINVAL' failed
FAIL test-symlink (exit status: 134)

Please let me know if I need to provide additional information.

Thank you very much for your response.

Tom Oppe






-----Original Message-----
From: Eric Blake [mailto:address@hidden] 
Sent: Thursday, September 5, 2019 9:17 AM
To: Oppe, Thomas C ERDC-RDE-ITL-MS Contractor <address@hidden>;
'address@hidden' <address@hidden>
Subject: Re: Test failure in GNU M4 1.4.18

On 9/5/19 6:07 AM, Oppe, Thomas C ERDC-RDE-ITL-MS Contractor wrote:
> Dear Sir:
> 
> I saw a test failure in the "make check" phase when building "m4-1.4.18"
> using GCC 6.3.0.  The error was:
> 
> ../build-aux/test-driver: line 107: 419398 Aborted                 (core
> dumped) "$@" > $log_file 2>&1
> FAIL: test-symlink

On which platform? That particular test comes from gnulib; it may be that
gnulib has fixed the problem in the test to work around your platform (in
which case, we just need a newer m4 release picking up newer gnulib) - but
it's hard to tell when you don't provide enough details.

> 
> Is this failure serious?

M4 doesn't create symlinks itself, so no, this failure is more an issue with
your platform being slightly different than what gnulib assumes (whether
that was the fault of your platform or of gnulib), and you can still use
your just-built m4 without worry.

--
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org

Attachment: smime.p7s
Description: S/MIME cryptographic signature


reply via email to

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