From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: flex package POSIX violation
Date: Sun, 31 Dec 2017 22:00:00 -0000 [thread overview]
Message-ID: <5a49530b.1d0b9d0a.17c20.f7f6@mx.google.com> (raw)
The POSIX standard, at least since 1997 [1], requires the presence of a "lex"
utility.
Most systems (including Cygwin) provide a Lex implementation via the "flex"
package. However with other OS, a "lex -> flex" symlink is provided, whereas the
Cygwin package does not.
Please resolve this, thanks.
[1] http://pubs.opengroup.org/onlinepubs/7908799/xcu/lex.html
--
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:[~2017-12-31 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 22:00 Steven Penny [this message]
2017-12-31 22:12 ` Marco Atzeri
2017-12-31 22:34 ` Yaakov Selkowitz
2017-12-31 23:43 ` Stephen John Smoogen
2018-01-05 14:37 ` Gerrit Haase
2018-01-06 0:17 ` Steven Penny
[not found] <CANnLRdjLkgpsw6ogipAVaAsjKm+fRruBFvizK-sgSNiXYWrijg@mail.gmail.com>
2018-01-01 0:26 ` Steven Penny
2018-01-01 0:55 ` Stephen John Smoogen
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=5a49530b.1d0b9d0a.17c20.f7f6@mx.google.com \
--to=svnpenn@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).