From: Ramakrishnan Muthukrishnan <vu3rdd@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: patch to check for GNU flex
Date: Sat, 20 Nov 2010 04:18:52 +0530 [thread overview]
Message-ID: <AANLkTikLn-xQ72xK0paGQZ44B9spo_rg+YD+dOxSoZeq@mail.gmail.com> (raw)
In-Reply-To: <87k4k9vsxs.fsf@gnu.org>
On Sat, Nov 20, 2010 at 4:09 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> Hi!
>
> Flex is only needed when building from Git, not when building from a
> tarball, which is why ‘configure’ doesn’t check for it. (And Flex is
Oh.. ok. Didn't know that.
> not GNU, BTW. ;-))
Didn't know that too! Thanks. :-)
--
Ramakrishnan
next prev parent reply other threads:[~2010-11-19 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 17:35 patch to check for GNU flex Ramakrishnan Muthukrishnan
2010-11-19 22:39 ` Ludovic Courtès
2010-11-19 22:48 ` Ramakrishnan Muthukrishnan [this message]
2010-11-20 22:23 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikLn-xQ72xK0paGQZ44B9spo_rg+YD+dOxSoZeq@mail.gmail.com \
--to=vu3rdd@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.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 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).