Re: rcs-5.8 test failures on HP-UX 11.31

[Paul Ackersviller]

Hi again,

Many apologies for taking so long for this reply... I'm not sure at this
point how much of my previous report may be still applicable.  I'm on a
slightly newer piece of hardware now, perhaps with some different vendor
patches, although my OS version is still the same.  The good and bad news
is that I'm not even able to get a successfult compile now.  I expect
at least that things should be easier to recify then.

Both different gcc version I have here end with
gcc -std=gnu99 -std=gnu99 -DHAVE_CONFIG_H -I. -I../lib  -I'../lib'    -g -MT 
ci.o -MD -MP -MF .deps/ci.Tpo -c -o ci.o ci.c
ci.c: In function 'main':
ci.c:678:15: error: 'help' undeclared (first use in this function)
ci.c:678:15: note: each undeclared identifier is reported only once for each 
function it appears in
ci.c:682:3: warning: implicit declaration of function 'CHECK_HV' 
[-Wimplicit-function-declaration]

However, since I'm not entirely sure how well gcc works on this platform
yet, I'm more inclined to use HP's compiler... but it ends similarly with

        source='ci.c' object='ci.o' libtool=no \
        DEPDIR=.deps depmode=hp2 /bin/sh ../build-aux/depcomp \
        cc -DHAVE_CONFIG_H -I. -I../lib  -I'../lib'    -AC99 -c ci.c
"ci.c", line 249: warning #2186-D: pointless comparison of unsigned integer 
with zero
            if (!removedlock && 0 <= (removedlock = removelock (targetdelta)))
                                  ^

"ci.c", line 678: error #2020: identifier "help" is undefined
        .help = help,
                ^

"ci.c", line 682: warning #2223-D: function "CHECK_HV" declared implicitly
    CHECK_HV ();
    ^


On Mon, Dec 26, 2011 at 10:19:02PM +0100, Thien-Thi Nguyen wrote:
> [CC restored -- please retain on followup.]
> 
> () Paul Ackersviller <address@hidden>
> () Thu, 3 Nov 2011 23:04:25 +0000
> 
>    > Could you please collect the respective TEST.d files from running
>    >
>    >   $ cd tests
>    >   $ make check VERBOSE=1 TESTS='t180 t420 t470 t999'
>    >
>    > into a .tar.xz (or .tar.gz) and post that?  Also,
>    > include the config.log file from the top-level dir.
>    > We can figure out what went wrong, perhaps, w/ that.