public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Yngve Svendsen <yngve.svendsen@clustra.com>
To: Milan Zamazal <pdm@zamazal.org>,
	GNU GNATS discussion <help-gnats@gnu.org>
Cc: bug-gnats@gnu.org,kevin_olds@emeraldsolutions.com
Subject: Re: gnats/303: GNATS 4.0 Makefile Error
Date: Tue, 16 Oct 2001 06:36:00 -0000	[thread overview]
Message-ID: <5.1.0.14.2.20011130211032.00bd47e0@10.10.1.1> (raw)
In-Reply-To: <87herc79ks.fsf@blackbird.zamazal.org>

At 13:00 30.11.2001 +0100, Milan Zamazal wrote:
> >>>>> "ko" == kevin olds <kevin_olds@emeraldsolutions.com> writes:
>
>     ko> I get an error saying that -o is an illegal option for yacc.
>
>Would anyone complain if we solved the problem by documenting that Bison
>and Flex are needed for complete GNATS rebuilding?  Trying to support
>all the proprietary versions of yacc and lex seems to be a useless
>effort to me.  I think it's not necessary, since the tarball will
>contain the generated *.c files, with a proper time stamp.  People
>interested in development can install Bison and Flex easily.

Agreed. Time spent solving this would surely be better spent on all the 
other small things that's holding up 4.0. Let's worry about this limitation 
after 4.0.

- Yngve


_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

  reply	other threads:[~2001-11-30 20:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E168pkm-0007D4-00@fencepost.gnu.org>
2001-10-15 13:43 ` Milan Zamazal
2001-10-16  6:36   ` Yngve Svendsen [this message]
2001-10-16 10:54     ` Milan Zamazal
2001-10-16  8:09 Dirk Bergstrom

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=5.1.0.14.2.20011130211032.00bd47e0@10.10.1.1 \
    --to=yngve.svendsen@clustra.com \
    --cc=bug-gnats@gnu.org \
    --cc=help-gnats@gnu.org \
    --cc=kevin_olds@emeraldsolutions.com \
    --cc=pdm@zamazal.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).