Re: Makefile operator -ot generate-parse-datetime tru64

[Bruno Haible]

Hi,

> I'm building GNU tar on Tru64.
> > uname -srm
> OSF1 V5.1 alpha

Note that we dropped support of this platform two years ago. [1]

This means: while we may apply patches that look right and don't
have impact on other platforms, we won't have time to discuss
more complex issues.

> The operator -ot causes errors.
> 
> Can you state this stuff more portability?

Unfortunately no. It was a big challenge already to come up
with a solution of the parallel-build problem that did not
rely on GNU make nor on extra utilities. [2]

> I'm doing this, which I realize is the wrong file, at least, and maybe not 
> ideal otherwise,
> otherwise you would not be using -ot:
> 
> 
> > diff  Makefile.in.orig Makefile.in
> 2896c2896
> <       @{ test -f $(srcdir)/parse-datetime.c && test ! 
> $(srcdir)/parse-datetime.c -ot $(srcdir)/parse-datetime.y; } || $(MAKE) 
> generate-parse-datetime
> ---
> >       $(MAKE) generate-parse-datetime
> 2898c2898
> <       @{ test -f $(srcdir)/parse-datetime-gen.h && test ! 
> $(srcdir)/parse-datetime-gen.h -ot $(srcdir)/parse-datetime.c; } || $(MAKE) 
> generate-parse-datetime
> ---
> >       $(MAKE) generate-parse-datetime
> 
> Sure, eventually I'll have GNU make, bash, etc., and I should cross build, 
> but I am starting with tar, natively.

Yup. When you are bootstrapping a port of several utilities, you have
to make temporary workarounds.

Bruno

[1] https://lists.gnu.org/archive/html/bug-gnulib/2019-07/msg00030.html
[2] https://lists.gnu.org/archive/html/bug-gnulib/2020-09/msg00046.html