public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: matt@codespunk.com
Subject: Re: Make error when compiling xserver-cygwin-1.14.1-1
Date: Sat, 15 Jun 2013 22:48:00 -0000	[thread overview]
Message-ID: <51BCEF1F.7020805@dronecode.org.uk> (raw)
In-Reply-To: <51BCE57E.9080101@codespunk.com>

On 15/06/2013 23:06, Matt D. wrote:
> The error appears to be here:
> 
> /bin/sh ../../ylwrap winprefslex.l .c winprefslex.c
> 
> 'winprefslex.c' is not created but ylwrap is not returning an error. This is
> unfamiliar territory for me but I'll see what I can do.
> 
> Off the top of your head, is there a way to slim this down to remove ylwrap?
> Maybe it will throw something helpful.

That doesn't look right.  I have:

/bin/sh ../../ylwrap winprefslex.l lex.yy.c winprefslex.c -- flex -i

$ ./ylwrap  --help
Usage: ylwrap [--help|--version] INPUT [OUTPUT DESIRED]... -- PROGRAM [ARGS]...

So, it looks like maybe something has gone wrong in the autofoolery as it
hasn't found the name of your lex successfully, but has still configured.

I think now might be an appropriate time to ask if you have all the
prerequisites listed in [1]?

http://x.cygwin.com/docs/cg/prog-build-prerequisites.html

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2013-06-15 22:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15 22:07 Matt D.
2013-06-15 22:48 ` Jon TURNEY [this message]
2013-06-16 12:37   ` Matt D.
2013-06-16 14:25     ` Jon TURNEY
2013-06-20 19:53       ` Jon TURNEY
  -- strict thread matches above, loose matches on Subject: below --
2013-06-15 18:21 Matt D.
2013-06-15 21:36 ` Jon TURNEY

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=51BCEF1F.7020805@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=matt@codespunk.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).