From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Standard LEX variable doesn't work in Make.
Date: Tue, 22 Nov 2016 21:16:00 -0000 [thread overview]
Message-ID: <11448207-52c8-6745-999f-48a4534bbc41@t-online.de> (raw)
In-Reply-To: <d06883e8208624afb5d094ebd3e78375@mail.kylheku.com>
Am 21.11.2016 um 17:57 schrieb Kaz Kylheku:
> I'm changing a FOSS project to rely more on standard Make
> vars such as CC and CFLAGS and such: use $(CC) for
> the compiler unless told otherwise, incorporate $(CFLAGS)
> if it is defined, and so forth. This is friendly toward
> distro package maintainers.
Not really. Package maintainers will almost universally expect your
source to have some kind of 'configure' script, which would take of this
and most other such properties for you.
> Anyway, even though my Cygwin installation has GNU Flex,
> the lex command is nonexistent; thus the $(LEX) Make
> variable fails.
It's not $(LEX) that's failing here; it's the way you form expectations
about what $(LEX) is supposed to be. The value of $(LEX) is clearly
documented to default to 'lex' (see "info make implicit implicit").
> If the installation has some sort of lex, the
> predefined $(LEX) variable should resolve to it.
No. LEX is a modifiable variable, for the express purpose that it be
set to what the system actually needs. Yes, that means _you_ are
supposed to do that (or to set up tools outside make to do it for you).
Morale: Make is not autoconf, nor does it want to be.
One final note: your report is in no way specific to Cygwin, so this is
almost certainly the wrong mailing list to send it to.
--
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 prev parent reply other threads:[~2016-11-21 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 17:33 Kaz Kylheku
2016-11-22 20:59 ` Ken Brown
2016-11-22 21:16 ` Hans-Bernhard Bröker [this message]
2016-11-25 19:54 ` Brian Inglis
2016-11-26 23:51 ` Hans-Bernhard Bröker
2016-11-27 3:04 ` Brian Inglis
2016-11-27 16:02 ` 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=11448207-52c8-6745-999f-48a4534bbc41@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).