public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Cygport: How to add -I m4 to autoreconf / aclocal?
Date: Wed, 05 Jun 2019 17:23:00 -0000	[thread overview]
Message-ID: <cb8d1612-1941-05c8-cfa3-e945ffe32588@t-online.de> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A178FD76C0D@IRSMSX102.ger.corp.intel.com>

Am 05.06.2019 um 11:53 schrieb Soegtrop, Michael:

The reason is that aclocal is missing a "-I m4" option to include the
local m4 subfolder. I wonder what I need to do in the cygport file to
add this. Or should this be added in gnome2_autogen.sh.

If that had to be done, that would constitute a clear upstream bug.
Well, either that or that file itself should not be there.

Are we building this from a tarball, or directly off the bleeding edge?

"Autogen" scripts like that should usually only exist in Git/SVN/CVS
versions of the source, but not in release tarballs.  Those are supposed
to be packaged with all autoconfigury already built and included, and
the autogen script itself left out instead.

> configure.ac:161: error: macro GTK_CHECK_BACKEND is not defined; is a m4 file missing?
> /usr/share/aclocal/ax_require_defined.m4:35: AX_REQUIRE_DEFINED is expanded from...
> configure.ac:161: the top level

The name prefix AX_ indicates a non-standard macro.  This particular one
is available in the autoconf-archive package in Cygwin (hence the
generic install location, instead of the version-specific ones where all
our actual aclocal versions' files are kept).  Linux distros may package
it differently.

But source packages using such non-standard macros may be assuming
different versions of them than we have.  Which is all the more reason
they really have to include them, in their own version control.

> I also wonder if the -install option to autoreconf shouldn't be forwarded to aclocal.

If autoreconf itself isn't doing that, we quite probably shouldn't, either.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2019-06-05 17:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05  9:53 Soegtrop, Michael
2019-06-05 17:23 ` Hans-Bernhard Bröker [this message]

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=cb8d1612-1941-05c8-cfa3-e945ffe32588@t-online.de \
    --to=hbbroeker@t-online.de \
    --cc=cygwin@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).