public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: Jack Pegler <jackpegler@gmail.com>
Subject: Re: https://github.com/alectrocute/flasksaas
Date: Wed, 25 Sep 2019 05:26:00 -0000	[thread overview]
Message-ID: <a9f814b6-f1f3-5d9f-36ff-affa3d7df2ec@SystematicSw.ab.ca> (raw)
In-Reply-To: <CANBMV9rxhYk1kXaoiGSASNftXEK_KserOw8PHZ6dnP3fW72B-g@mail.gmail.com>


On 2019-09-23 23:22, Jack Pegler wrote:
> On Tue, 24 Sep 2019 at 08:13, <cygwinautoreply@sourceware.org> wrote:
>>> Awesome job on the above. Tried downloading and running and the make dev
>>> line throws this error
>>> 0 [main] make 13900 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
>>> pointer.  Please report this problem to
>>> the public mailing list cygwin@cygwin.com
>>> make: date: Command not found
>>> make: basename: Command not found
>>> cd app && ln -sf config_dev.py config.py
>>> make: /bin/sh: Command not found
>>> Makefile:17: recipe for target `dev' failed
>>> make: *** [dev] Error 127

> Thanks a bunch. I was running on my windows machine which is *always* the 
> issue.> this got things working.>
https://stackoverflow.com/questions/55535406/how-to-solve-the-traceback-error-when-it-is-not-a-code-issue/55540904#55540904

Please raise issues with github projects on github.
Lots of projects use Cygwin that Cygwin volunteers know nothing about.
Most of those projects also never update their packaged Cygwin release,
resulting in these messages when someone runs it on a newer Windows release.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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:[~2019-09-24 23:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24  5:13 https://github.com/alectrocute/flasksaas Jack Pegler
2019-09-24  5:22 ` https://github.com/alectrocute/flasksaas cygwinautoreply
2019-09-24  7:05   ` https://github.com/alectrocute/flasksaas Jack Pegler
2019-09-25  5:26     ` Brian Inglis [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=a9f814b6-f1f3-5d9f-36ff-affa3d7df2ec@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    --cc=jackpegler@gmail.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).