bug-gnucobol
[Top][All Lists]
Advanced

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

Re: [Bug-GnuCOBOL] [GnuCOBOL 3.0-rc1] testsuite: 583 637 858 failed, 787


From: Simon Sobisch
Subject: Re: [Bug-GnuCOBOL] [GnuCOBOL 3.0-rc1] testsuite: 583 637 858 failed, 787 passed unexpectedly
Date: Tue, 21 May 2019 00:42:53 +0200
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1

Thank you for the report and the notes so far.
Those failures should be fixed with current development version. Can you
please test the snapshot from

https://ci.appveyor.com/api/projects/GitMensch/trunk/artifacts/gnucobol-3.1-dev.tar.gz?job=Image:%20Ubuntu1804

[you may use lz or xz, too]

This would be especially useful as s390x builds are relative rare.

Notes:
* there are currently two known issues which will be fixed "soon":
  * needs GNU make (should be the default on SLES, so likely no issue)
  * tests 900-901 fail
* if you have a perl binary available or can get it, please also run
  make test and report back
* it _may_ be even better to specify the option in the compiler setting
  instead CLAGS: ./configure "CC=gcc -m64"

Again: thank you for the note and thank you for the follow-up to come.

Simon

Am 20.05.2019 um 21:00 schrieb Jeffrey Barnard:
> Additional information for this bug report ...
>
> Installation on SLES-15 for s390x.
>
> I looked at the release notes for SLES 15
> (https://www.suse.com/releasenotes/s390x/SUSE-SLES/15/#fate-325552) and
> it says that "Building 32-bit applications is not supported on SUSE
> Linux Enterprise 15." There are a few items that are intended to support
> "tools to set up software or hardware." I would say that none of those
> exist on the mainframe, so none of that support is there for s390x.
>
> So, s390x is not 32 and 64 bit. It is now 64-bit only.
>
> ./configure CFLAGS=-m64
> would seem to help here.
>
> ERROR: 899 tests were run,
> 1 passed unexpectedly,
> 12 failed (9 expected failures).
> 2 tests were skipped.
>
>
> Jeff Barnard



reply via email to

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