emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-bug-tracker] bug#7828: closed (Documentation about '-d' in AM_YFL


From: GNU bug Tracking System
Subject: [Emacs-bug-tracker] bug#7828: closed (Documentation about '-d' in AM_YFLAGS is suboptimal)
Date: Wed, 12 Jan 2011 22:51:02 +0000

Your message dated Wed, 12 Jan 2011 23:57:55 +0100
with message-id <address@hidden>
and subject line Re: documentation about '-d' in AM_YFLAGS is suboptimal
has caused the GNU bug report #7828,
regarding Documentation about '-d' in AM_YFLAGS is suboptimal
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
7828: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7828
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Fwd: header file from yacc doesn't go to a distribution (automake 1.11) Date: Wed, 12 Jan 2011 12:21:19 +0300
Package isn't enclosed because otherwise the message doesn't get through.

> Finally had time to make some tests, and now i've got it:)
>
> When i set AM_YFLAGS to -dt it doesn't distribute a header, probably
> because it's searching for -d to be alone.
> When i set AM_YFLAGS = -d -t, it works.
>
> A small test package enclosed.
>
> 2010/8/1 Ralf Wildenhues <address@hidden>:
>> Hi Юрий,
>>
>> * Юрий Пухальский wrote on Wed, Jul 28, 2010 at 03:38:11PM CEST:
>>> In the documentation it's stated that "The intermediate files
>>> generated by yacc (or lex) will be included in any distribution that
>>> is made. That way the user doesn't need to have yacc or lex."
>>> But albeit the .c files are included, the corresponding .h file isn't.
>>>
>>> Likewise there is no rule to build a missing header file.
>>
>> Please show a small example where this fails for you.
>>
>> Thanks,
>> Ralf
>>
>
>
>
> --
> «The good thing about standards is there are so many to choose from.»
>



-- 
«The good thing about standards is there are so many to choose from.»



--- End Message ---
--- Begin Message --- Subject: Re: documentation about '-d' in AM_YFLAGS is suboptimal Date: Wed, 12 Jan 2011 23:57:55 +0100 User-agent: KMail/1.13.3 (Linux/2.6.30-2-686; KDE/4.4.4; i686; ; )
On Wednesday 12 January 2011, Ralf Wildenhues wrote:
> 
> OK with nits addressed.
> 
> Thanks!
> Ralf
>
> [CUT]
> 
> > From a report by ???????? ????????????????????.
> 
> My email client renders this as a bunch of question marks only.  Please
> ensure that both the git log entry and the ChangeLog entry are properly
> encoded in UTF-8.
>
They should be (they both looks ok in vim with :set enc=utf-8).

> > --- a/doc/automake.texi
> > +++ b/doc/automake.texi
> > @@ -6078,7 +6078,12 @@ intended for the @file{Makefile.am} author.
> >  @code{AM_YFLAGS} is usually used to pass the @option{-d} option to
> >  @command{yacc}.  Automake knows what this means and will automatically
> >  adjust its rules to update and distribute the header file built by
> > address@hidden -d}.  What Automake cannot guess, though, is where this
> > address@hidden address@hidden note that @command{automake} recognizes
> > address@hidden in @code{AM_YFLAGS} only if it is not clustered with other
> > +options; for example, it won't be recognized if @code{AM_YFLAGS} is
> > address@hidden, but it will be if @code{AM_YFLAGS} is @samp{-d -t} or
> > address@hidden -d}.}.
> 
> Generally, @footnote's should be used sparingly, as they disrupt the
> flow of reading and don't render well in the info output.  I guess it's
> acceptable here though.
> 
> Please use @option for denoting the options here.
>
OK.  Sorry for the noise, but for some stupid reason I thought that using
@option with more (whitespace-separated) arguments was inappropriate.  Go
figure.

Merged into maint and yacc-work, and merged both into master.

Thanks,
  Stefano


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]