On 2017-10-18 09:11, Corinna Vinschen wrote: > On Oct 18 07:52, Ken Brown wrote: >> On 10/18/2017 6:13 AM, Corinna Vinschen wrote: >>> On Oct 17 18:36, Jeffrey Walton wrote: >>>> On Mon, Oct 16, 2017 at 3:12 AM, Jeffrey Walton wrote: >>>>> Hi Everyone, >>>>> >>>>> I'm trying to build Emacs on Cygwin. I use the platform as a test bed >>>>> because of Newlib. Emacs is failing with: >>>> >>>> Forgive my ignorance... Should this question go to the Newlib folks? >>> >>> Good thinking, but in this case, no. The problem (*iff* there is any) >>> and the potential fix would only affect Cygwin headers. >> >> As I said in https://cygwin.com/ml/cygwin/2017-10/msg00144.html, this is >> almost certainly the same gnulib issue that has already been fixed >> (http://lists.gnu.org/archive/html/bug-gnulib/2016-03/msg00054.html). The OP >> is probably building old emacs sources that hadn't incorporated the fix. > > Yeah, I saw that, Ken, but thanks for pointing it out. I was > talking about this more in a theoretical way :) I don't think there is anything more to do on our end wrt this gnulib issue. -- Yaakov Selkowitz Software Engineer - Platform Enablement Group Red Hat, Inc.