From: "Jannick" <thirdedition@gmx.net>
To: <cygwin@cygwin.com>
Subject: RE: [PATCH] glob.h (i686-pc-mingw32) b/c wrong function prototype of function 'glob'
Date: Sat, 08 Jul 2017 08:33:00 -0000 [thread overview]
Message-ID: <003001d2f7c4$cae6a6d0$60b3f470$@gmx.net> (raw)
In-Reply-To:
On Jul 03, 2017 at 01:12 PM, Jannick wrote:
> of function 'glob'
>
> On Mon, 3 Jul 2017 09:25:51 +0200, Corinna Vinschen wrote:
>
> > This is, in fact, the wrong mailing list. The files for the mingw
> > cross build environment are maintained via the mingw-w64-public
> > mailing list on sourceforge, see
> >
> > https://sourceforge.net/p/mingw-w64/mailman/
> >
> > Ideally you provide your patches there.
>
> Thanks for this - just for the record: https://sourceforge.net/p/mingw-w64/mailman/message/35924907/
The mingw-w64 list turned out to be the wrong list, too, unfortunately.
For the MinGW32 distribution glob.h is maintained here
https://sourceforge.net/p/mingw/mingw-org-wsl/ci/5.0-active/tree/mingwrt/include/glob.h.
I am not sure what the code basis of i686-pc-mingw32 is, so am back here on this list with the patch.
Maybe there is someone out here who knows how which version of glob.h finds its way into cygwin's
i686-pc-mingw32 distribution.
Kind regards,
J.
--
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:[~2017-07-08 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 13:44 Jannick
2017-07-03 7:26 ` Corinna Vinschen
2017-07-03 11:12 ` Jannick
2017-07-08 8:33 ` Jannick [this message]
2017-07-08 12:45 ` Jon Turney
2017-07-08 15:14 ` Jannick
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='003001d2f7c4$cae6a6d0$60b3f470$@gmx.net' \
--to=thirdedition@gmx.net \
--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).