public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: Cygwin Applications <cygwin-apps@cygwin.com>
Subject: CI scallywag setup/cygport/autoconf missing autoconf-archive pkg
Date: Wed, 29 Sep 2021 22:15:53 -0600	[thread overview]
Message-ID: <9b1ea563-f5c0-04f2-d117-6f792b6cdb94@SystematicSw.ab.ca> (raw)

Hi folks,

Autotools needs m4 macros in autoreconf-archive to config for gcov and 
other dependencies or build fails with e.g.

"configure.ac:33: error: possibly undefined macro: AX_CODE_COVERAGE
    If this token and others are legitimate, please use m4_pattern_allow.
    See the Autoconf documentation."

CI scallywag setup does not install nor does cygport nor autoconf 
require autoconf-archive so packages have to include in BUILD_REQUIRES.

As autoconf requires: autoconf2.1 autoconf2.5 bash sed, I believe that 
would be the more appropriate place for an autoconf-archive requirement, 
otherwise cygport would have to require it, which is not so obvious.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

             reply	other threads:[~2021-09-30  4:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30  4:15 Brian Inglis [this message]
2021-10-01 21:37 ` Yaakov Selkowitz
2021-10-02  0:06   ` Brian Inglis
2021-10-02  4:15 ` Achim Gratz
2021-10-02  5:48   ` Brian Inglis
2021-10-02 14:13     ` Ken Brown
2021-10-02 16:35       ` Brian Inglis
2021-10-03 19:14         ` Brian Inglis

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

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

  git send-email \
    --in-reply-to=9b1ea563-f5c0-04f2-d117-6f792b6cdb94@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-apps@cygwin.com \
    /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).