🚀 go-pugleaf

    Hi there. I have had some problems building GNU tar 1.11 on an SGI Iris,
running IRIX 4.0.4:

1.  The public routine valloc() is defined in both port.c and malloc.c. This
    causes a link error. My workaround is to compile with "-DHAVE_VALLOC",
    which causes port.c to ignore its definition of valloc().

2.  If getdate.y is parsed with bison, the generated C code contains
    references to alloca(). Now under IRIX, alloca() is a std C library
    routine, and it requires alloca.h to be brought in for correct compilation.
    alloca.h is not brought in, for two reasons:

    1.  The #include <alloca.h> at the top of getdate.y does not test for
        the manifest define HAVE_ALLOCA_H. (And looking in getopt.c, getdate.y
        seems to be missing a lot of other tests as well).

    2.  There are no rules in the Makefile for building a .o from a .y.
        make therefore uses its internal rules, which will not reference the
        make variable "DEFS", where all the manifest defines are setup. So
        y.tab.c never knows about HAVE_ALLOCA_H.

3.  There is a commented out line in the Makefile, just above the target
    "all", for the definition of "AUX", which seems to cause problems with
    make under IRIX - make will not recognize the "all". Deleting the
    commented out line solves the problem.

4.  In the Makefile, for the target "install", it tries to install tar.info,
    which is not supplied with the pkg.

5.  I compiled GNU tar on the Iris in K&R mode (cc -cckr). The IRIX
    pre-processor when invoked in this mode complains about any whitespace
    present on a line prior to a pre-processor statement (e.g. " #ifdef").
    I edited the files buffer.c, create.c, extract.c, getopt.c, port.h and
    regex.c to remove such whitespace.


Eventually, I was able to build tar, but now it core dumps :-). I'll let you
know if I find anything.

Thanks for your time.


Chris Moran
chris.moran@mincom.oz.au