public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>,
	"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 08:03:00 -0000	[thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A178FD7FDEF@IRSMSX102.ger.corp.intel.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2029 bytes --]

Dear Hans-Bernhard,

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

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.
 
> If that had to be done, that would constitute a clear upstream bug.
> Well, either that or that file itself should not be there.

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. If this is the intended behavior of aclocal, this is a regression in current cygwin's aclocal package are some of the packages it requires.

- In the past cygport automatically added an option to autoreconf to include the local m4 folder.

- The original builder/maintanier of the current package mingw64-x86_64-gtksourceview3.0-3.24.6 did something non-standard to get the package build (that is didn't just run cygport ... all.

- The use of AX_REQUIRE_DEFINED in gtksourceview configure.ac for macros defined in the package local m4 folder is bogus. This would then be a gtksourceview upstream bug, as you suggest. One can argue that it doesn't make a lot of sense to check the availability of locally supplied macros, but one can also ask why it seems to work on other systems and seems to have worked on Cygwin in the past.

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
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

             reply	other threads:[~2019-06-06  8:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06  8:03 Soegtrop, Michael [this message]
2019-06-06 19:18 ` Hans-Bernhard Bröker
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=0F7D3B1B3C4B894D824F5B822E3E5A178FD7FDEF@IRSMSX102.ger.corp.intel.com \
    --to=michael.soegtrop@intel.com \
    --cc=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).