public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin TCP slow
Date: Fri, 02 Dec 2016 23:08:00 -0000	[thread overview]
Message-ID: <5841FEE5.8010101@maxrnd.com> (raw)
In-Reply-To: <CAO1c0AR9SPdvq6tVifZ18Ev+vp9oWd0wThbj0BqeLPk9qVmTFA@mail.gmail.com>

Daniel Havey wrote:
> 2.) Here is the cygcheck.out file with all that information.
> The make is failing because of some device configuration.
>
> /home/dahavey/oss/src/newlib-cygwin/winsup/cygwin/gendevices: shilka
> command missing? - No such file or directory
> make[3]: *** [Makefile:720:
> /home/dahavey/oss/src/newlib-cygwin/winsup/cygwin/devices.cc] Error 2
> make[3]: Leaving directory
> '/home/dahavey/oss/build/x86_64-unknown-cygwin/winsup/cygwin'
> make[2]: *** [Makefile:81: cygwin] Error 1
> make[2]: Leaving directory
> '/home/dahavey/oss/build/x86_64-unknown-cygwin/winsup'
> make[1]: *** [Makefile:9464: all-target-winsup] Error 2
> make[1]: Leaving directory '/home/dahavey/oss/build'
> make: *** [Makefile:883: all] Error 2
>
> /home/dahavey/oss/src/newlib-cygwin/winsup/cygwin/gendevices doesn't
> exist in the sources that I downloaded from the cygwin website using:
> git clone git://sourceware.org/git/newlib-cygwin.git
> Something is not right here :).

The canonical build instructions for the Cygwin DLL are in the FAQ...
https://cygwin.com/faq.html#faq.programming.building-cygwin

You might want to look over the first paragraph there to avoid stumbling over 
the next requirement ;)

..mark


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

      parent reply	other threads:[~2016-12-02 23:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29  1:25 Daniel Havey
2016-11-29  5:56 ` Brian Inglis
2016-11-30  9:16   ` Daniel Havey
2016-11-30 10:09     ` Sam Habiel
2016-11-30 10:44       ` Brian Inglis
2016-11-30 16:00         ` Lee
     [not found]         ` <CAD8GWss1zb1J7m3Knf1TGuAPcVKQVNFXgt2uX02o_Z08ZOfEOw@mail.gmail.com>
2016-12-02 20:29           ` Daniel Havey
2016-12-02 22:37             ` Brian Inglis
2017-01-04 21:33               ` Daniel Havey
2016-12-02 23:08             ` Mark Geisert [this message]

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=5841FEE5.8010101@maxrnd.com \
    --to=mark@maxrnd.com \
    --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).