From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Cygport: How to add -I m4 to autoreconf / aclocal?
Date: Wed, 05 Jun 2019 09:53:00 -0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A178FD76C0D@IRSMSX102.ger.corp.intel.com> (raw)
Dear Cygwin Team,
recompiling the package "mingw64-x86_64-gtksourceview3.0-3.24.6" from sources with cygport (In order to generate the debug info) I found that the compile step fails. Aclocal fails in a few macro availability checks. 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. Autoreconf is called there like this:
autoreconf --verbose --force --install -Wno-portability
which leads to this aclocal call:
autoreconf-2.69: running: aclocal-1.15 --force --warnings=no-portability
which leads to this failure:
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
autom4te-2.69: /usr/bin/m4 failed with exit status: 1
:
*** ERROR: gnome2: autoreconf failed
It might also be that some global configuration has changed. The strange thing is that the files in the ./m4 folder make it into the aclocal.m4 file, but aclocal also runs m4 including all available files and in this run the files in ./m4 are not included, which leads to the above failure.
I also wonder if the -install option to autoreconf shouldn't be forwarded to aclocal.
Btw.: mingw64-x86_64-gtksourceview3.0-3.24.6 has a rather bad bug (it frees all data structures on any thread exit rather than process exit) which is fixed upstream since a while. Maybe the autoconf issue is the reason why the package has not been updated by the maintainer.
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
--
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
next reply other threads:[~2019-06-05 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 9:53 Soegtrop, Michael [this message]
2019-06-05 17:23 ` Hans-Bernhard Bröker
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=0F7D3B1B3C4B894D824F5B822E3E5A178FD76C0D@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--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).