From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Roger Pau Monne <roger.pau@entel.upc.edu>, xen-devel@lists.xen.org
Subject: Re: [PATCH] configure: do not require Bison
Date: Wed, 29 Feb 2012 15:53:34 +0100 [thread overview]
Message-ID: <20120229145334.GA26404@aepfle.de> (raw)
In-Reply-To: <1330525507-7833-1-git-send-email-ian.campbell@citrix.com>
On Wed, Feb 29, Ian Campbell wrote:
> I _think_ this isn't required because we also checkin the generated files. A
> more complete fix might also allow the user to force regeneration but I didn't
> both here.
Perhaps flex is not really needed as well, at least it wasnt before the
change to configure. But then, both are needed if one updates .y and .l
files.
Olaf
next prev parent reply other threads:[~2012-02-29 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 14:25 [PATCH] configure: do not require Bison Ian Campbell
2012-02-29 14:51 ` Roger Pau Monné
2012-02-29 15:00 ` Ian Campbell
2012-02-29 15:09 ` Roger Pau Monné
2012-02-29 16:23 ` Ian Campbell
2012-02-29 17:02 ` Ian Jackson
2012-02-29 16:35 ` Ian Jackson
2012-02-29 14:53 ` Olaf Hering [this message]
2012-02-29 14:56 ` David Vrabel
2012-02-29 15:01 ` Ian Campbell
2012-02-29 16:30 ` Ian Jackson
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=20120229145334.GA26404@aepfle.de \
--to=olaf@aepfle.de \
--cc=ian.campbell@citrix.com \
--cc=roger.pau@entel.upc.edu \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.