From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 113405 invoked by alias); 1 Jan 2018 00:26:28 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 113372 invoked by uid 89); 1 Jan 2018 00:26:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=demonstration, Hx-languages-length:919, H*M:google, H*UA:github.com X-HELO: mail-oi0-f54.google.com Received: from mail-oi0-f54.google.com (HELO mail-oi0-f54.google.com) (209.85.218.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 01 Jan 2018 00:26:25 +0000 Received: by mail-oi0-f54.google.com with SMTP id w125so31544851oie.7 for ; Sun, 31 Dec 2017 16:26:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:to:references:subject :user-agent; bh=4psClbASJAN1lWJEv7xrPlscMbjhBgJtHTkXcI9f+UU=; b=JqplZKsU+6GePuB2SFz9mO5qn1CRHBlNAJ8p94eLzTVtiXh3P3FgW3ObjNu3rOtXbG pMZxwmPNeS+NkGSXL8d0gyg3Un9jDeGMFItdsC2bKo4GeeSDzNKfFDI0cP/BA7TJgNGN K4mzKUHIRZIAUlpI8iJbc1xONav9cbJezwWVkLZt3TnseU66bVXAqCwO3/POQha3B2As KsVhW+XWs/xAD03ADdl+RFBbQ8dCfTDJNK3dZsmGsd83EtrnuY0GH8+p8aZFYAUNG3DH ZWC1DiTiZpBI59rXE3M6plzV1dnl22uvrjz8Mn9Wc9DET5YZ9jxZjMmLInFAIYlbJR5V FVJg== X-Gm-Message-State: AKGB3mJvfrP6SRvXb33qoNcCl7DBfLwybG3MPdeONv9J2yDunWMP/m7f A4L60a7gPUozjtsxPwHmWSNrfQ== X-Google-Smtp-Source: ACJfBou3F7CCY8TfZ3hXW4A3euJGHFM4ZJNUQK18SfKyqfxlRhvURqYSqrQ1cODQw34vfBe2as/uGg== X-Received: by 10.202.117.141 with SMTP id q135mr31490943oic.109.1514766383606; Sun, 31 Dec 2017 16:26:23 -0800 (PST) Received: from 3H6 ([2605:6000:9fc0:56:c54d:2844:d0c:ba]) by smtp.gmail.com with ESMTPSA id t124sm17332759oih.48.2017.12.31.16.26.22 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 31 Dec 2017 16:26:22 -0800 (PST) Message-ID: <5a49802e.82f5ca0a.48f96.8a5b@mx.google.com> Date: Mon, 01 Jan 2018 00:26:00 -0000 From: Steven Penny X-Google-Original-From: Steven Penny To: cygwin@cygwin.com References: Subject: Re: flex package POSIX violation Content-Type: text/plain; charset=utf8; format=flowed User-Agent: Tryst/2.0.1 (github.com/svnpenn/tryst) X-SW-Source: 2018-01/txt/msg00000.txt.bz2 On Sun, 31 Dec 2017 18:43:00, Stephen John Smoogen wrote: > Which is why I wanted to see where this was going. Are these fixes > just looking for low hanging fruit to be POSIX compliant, or are these > needing larger amounts of resources to be 'compliant'? If the > flex->lex link fails some sort of POSIX test, are people going to need > Cygwin porters to fix those? Also is there an easy line for "this is > compliant enough?" Here is a simple demonstration of the problem: $ cat xr.l %option main %% ya printf("zu"); %% $ make xr lex -t xr.l > xr.c /bin/sh: lex: command not found make: *** [: xr.c] Error 127 rm xr.c now of course you can work around this by "make LEX=flex xr" or similar, but no major Linux distro makes you do this, as they already include "lex" vis-a-vis the symlink to flex. [1] http://gnu.org/software/make/manual/html_node/Implicit-Variables -- 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