Re: rcs-5.9.4: make check: tests 510 511 603 604 605 900 999 failed on AIX

Michael Felt <[email protected]> Tue, 27 Jan 2015 10:53:34 +0100
Newsgroups gmane.comp.version-control.rcs.bugs
Message-ID <CANvxniU1Te8tcYAn1jsC9=ynCd=MZ=2RkY_6hHD5zjAopqDnUA@mail.gmail.com>
I shall save the old, unpack the distribution (or do you have an rsync/git
URL I could use?) - I try to stay 'limited' to distributions.

And/or I could give you access to my AIX system I am testing on (x064 -
which is with IBM compiler, and x065 which has gcc installed).

The later is perhaps easier for both of us. However, I would need a
personal email to exchange info on how to connect.

On Tue, Jan 27, 2015 at 10:17 AM, Thien-Thi Nguyen <[email protected]> wrote:

> () Michael Felt <[email protected]>
> () Mon, 26 Jan 2015 19:49:00 +0100
>
>    I have always 'remembered' RCS as a directory where the
>    comma-v files were stored, so I was not surprised to see RCS
>    as a directory.
>
> Normally, "RCS" is a directory containing comma-v files.  RCS
> should be able to operate just fine with the comma-v in the same
> directory as the working file, however.  For most of the tests,
> "x" is the working file and "x,v" is the comma-v file (all in
> the same tNNN.d directory).
>
> I'm beginning to think that specifying ‘--disable-threads’ is
> not the right approach, and that propagating the makefile var
> ‘LIBTHREAD’ as determined by the configure script, is.  Perhaps
> something in gnulib is not so flexible and was not fully tested
> w/ threads disabled under AIX.  So, i've just installed:
>
>  http://git.savannah.gnu.org/cgit/rcs.git/commit/?h=p&id=cdc017067
>  http://git.savannah.gnu.org/cgit/rcs.git/commit/?h=p&id=6dd5ca388
>
> which do that for "make" and "make check" flows, respectively.
> Could you please apply these patches to the freshly-unpacked
> Makefile.in files in src/ and tests/, respectively:
>
>
>
> then configure (*without* ‘--disable-threads’) and "make" and
> "make check VERBOSE=1"?
>
>    What puzzles me though is that the same errors are reported -
>    but/and there are err files in test-dirs that passed.
>
>    root@x064:[/data/test/rcs-5.9.4]make VERBOSE=1 check
>    [...]
>
> That's not a problem.  For most tests, the test infrastructure
> splits stdout/stderr unconditionally (in tests/common, see shell
> func ‘split_std_out_err’).
>
>    On Mon, Jan 26, 2015 at 3:13 PM, Thien-Thi Nguyen <[email protected]> wrote:
>    [...]
>
> Could you please omit this bottom-citing in future posts?
> We prefer to avoid top-posting on GNU mailing lists, generally.
> TIA for your cooperation on this.
>
> --
> Thien-Thi Nguyen
>    GPG key: 4C807502
>    (if you're human and you know it)
>       read my lisp: (responsep (questions 'technical)
>                                (not (via 'mailing-list)))
>                      => nil
>
>