From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Cygport: How to add -I m4 to autoreconf / aclocal? (issue with building mingw64-x86_64-gtksourceview3.0-3.24.6 )
Date: Thu, 06 Jun 2019 19:18:00 -0000 [thread overview]
Message-ID: <6a834f72-b21a-6fa5-1e72-5e1190d5a0f7@t-online.de> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A178FD7FDEF@IRSMSX102.ger.corp.intel.com>
Am 06.06.2019 um 10:03 schrieb Soegtrop, Michael:
> From a tarball. As far as I can tell I am exactly reproducing the
> original package that is available as binary on Cygwin repos with
> exactly the same sources, patches and cygport file.
... but possibly way different versions of the autotools compared to
those the package was built with, back then.
> I can't judge this and would need some advice here. The issue could
> be at several places:
>
> - In the past and on other systems aclocal automatically included the
> package local m4 folder in all process steps.
Possible. Automake may have changed in that regard, at some point.
Still that would constitut, if not a flat-out bug, at least severe
bit-rot in the upstream package, because if it doesn't work with
Cygwin's automake version 1.15, it most likely doesn't with reasonably
current versions of automake on other platforms, either.
> - In the past cygport automatically added an option to autoreconf to
> include the local m4 folder.
I rather doubt that.
--
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 prev parent reply other threads:[~2019-06-06 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 8:03 Soegtrop, Michael
2019-06-06 19:18 ` Hans-Bernhard Bröker [this message]
2019-06-06 19:43 ` Soegtrop, Michael
2019-06-06 21:28 ` Hans-Bernhard Bröker
2019-06-08 13:40 ` Soegtrop, Michael
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=6a834f72-b21a-6fa5-1e72-5e1190d5a0f7@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).