From: Jack Pegler <jackpegler@gmail.com>
To: cygwin@cygwin.com
Subject: https://github.com/alectrocute/flasksaas
Date: Tue, 24 Sep 2019 05:13:00 -0000 [thread overview]
Message-ID: <CANBMV9ohDOth-8ych_u4Re0Zz3BEOWrvHedzehumWc416m_rAA@mail.gmail.com> (raw)
Hey,
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!
Jack Pegler
--
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 reply other threads:[~2019-09-24 5:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 5:13 Jack Pegler [this message]
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 ` https://github.com/alectrocute/flasksaas Brian Inglis
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=CANBMV9ohDOth-8ych_u4Re0Zz3BEOWrvHedzehumWc416m_rAA@mail.gmail.com \
--to=jackpegler@gmail.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).