public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: GIT source build failure: wcwidth.c::_wcwidth misses __locale_cjk_lang()
Date: Sun, 21 Aug 2016 15:25:00 -0000	[thread overview]
Message-ID: <ac2b1ee9-4885-c321-e0f9-678acfda2d95@t-online.de> (raw)
In-Reply-To: <20160821103028.n7via5q3t4xbusjx@calimero.vinschen.de>

Am 21.08.2016 um 12:30 schrieb Corinna Vinschen:

> thanks for the report, but I can't reproduce this.  I can build Cygwin
> fine natively as well as on Linux, with and without optimization.

That's strange.  On Re-examination, it builds here, too, even without 
the added include.  I.e. effectively it took only a `touch` of wcwidth.c 
to fix this.

Could there be a problem with the dependency handling in the newlib 
auto-foo which caused changes to header files to fail triggering a rebuild?

And while I'm at it: what _is_ the dependency handling here, anyway?  I 
can't seem to find any.  Which could indeed explain the problem.

> So why does this fail for you?  I wonder if some compile time settings
> are responsible for this problem.  How do you build Cygwin from the git
> repo?  Do you use some special debug options or something like that?

None that I'm aware of.  The only differences in may sandbox prior to 
occurence of the failure were in winsup/doc Makefile.in and configure. 
Other than that it's a straight-up

   ../newlib-cygwin/configure --prefix=/home/hbbro/prg/cygwin/inst

build.



--
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

  reply	other threads:[~2016-08-21 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21  4:01 Hans-Bernhard Bröker
2016-08-21 15:04 ` Corinna Vinschen
2016-08-21 15:25   ` Hans-Bernhard Bröker [this message]
2016-08-21 22:03     ` Corinna Vinschen
2016-08-22  1:31       ` 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=ac2b1ee9-4885-c321-e0f9-678acfda2d95@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).