bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Jay K <jayk123@hotmail.com>
To: "bug-gnulib@gnu.org" <bug-gnulib@gnu.org>
Cc: Larkin Nickle <me@larbob.org>
Subject: Makefile operator -ot generate-parse-datetime tru64
Date: Tue, 29 Jun 2021 08:17:22 +0000	[thread overview]
Message-ID: <MWHPR1401MB19511AE92ADF4922E583AA4AE6029@MWHPR1401MB1951.namprd14.prod.outlook.com> (raw)

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

The operator -ot causes errors.

Can you state this stuff more portability?

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.

Thank you,
  - Jay

             reply	other threads:[~2021-06-29 12:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29  8:17 Jay K [this message]
2021-06-29  8:24 ` getprocname Tru64 Jay K
2021-06-29 15:04   ` Bruno Haible
2021-07-06 11:25     ` Jay K
2021-06-29 14:52 ` Makefile operator -ot generate-parse-datetime tru64 Bruno Haible
2021-07-01 17:41 ` Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MWHPR1401MB19511AE92ADF4922E583AA4AE6029@MWHPR1401MB1951.namprd14.prod.outlook.com \
    --to=jayk123@hotmail.com \
    --cc=bug-gnulib@gnu.org \
    --cc=me@larbob.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).