* Wrong version displayed in documentation pdfs
@ 2017-01-06 9:47 Freddie Chopin
2017-01-06 19:36 ` Hans-Bernhard Bröker
0 siblings, 1 reply; 3+ messages in thread
From: Freddie Chopin @ 2017-01-06 9:47 UTC (permalink / raw)
To: newlib
Hi!
When building pdf documentation for libc and libm out of the most
recent package (2.5.0), the version on front page in both document says
2.2.0 with "December 2014" date.
Is there any way to make this value automatic, so it wouldn't have to
be updated with each release?
$ grep -R '2\.2\.0'
libm/libm.texinfo:@subtitle @code{libm} 2.2.0
libc/libc.texinfo:@subtitle @code{libc} 2.2.0
...
$ grep -R 'December 2014'
libm/libm.texinfo:@subtitle December 2014
libc/libc.texinfo:@subtitle December 2014
Regards,
FCh
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Wrong version displayed in documentation pdfs
2017-01-06 9:47 Wrong version displayed in documentation pdfs Freddie Chopin
@ 2017-01-06 19:36 ` Hans-Bernhard Bröker
2017-01-09 15:23 ` Corinna Vinschen
0 siblings, 1 reply; 3+ messages in thread
From: Hans-Bernhard Bröker @ 2017-01-06 19:36 UTC (permalink / raw)
To: Freddie Chopin, newlib
Am 06.01.2017 um 10:47 schrieb Freddie Chopin:
> Hi!
>
> When building pdf documentation for libc and libm out of the most
> recent package (2.5.0), the version on front page in both document says
> 2.2.0 with "December 2014" date.
>
> Is there any way to make this value automatic, so it wouldn't have to
> be updated with each release?
Automake does indeed offer such a mechanism (see "info automake doc
texinfo" about 'version.texi'); even the truly ancient version newlib
needs for --cygnus mode does.
Newlib just doesn't use it.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Wrong version displayed in documentation pdfs
2017-01-06 19:36 ` Hans-Bernhard Bröker
@ 2017-01-09 15:23 ` Corinna Vinschen
0 siblings, 0 replies; 3+ messages in thread
From: Corinna Vinschen @ 2017-01-09 15:23 UTC (permalink / raw)
To: newlib
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
On Jan 6 20:36, Hans-Bernhard Bröker wrote:
> Am 06.01.2017 um 10:47 schrieb Freddie Chopin:
> > Hi!
> >
> > When building pdf documentation for libc and libm out of the most
> > recent package (2.5.0), the version on front page in both document says
> > 2.2.0 with "December 2014" date.
> >
> > Is there any way to make this value automatic, so it wouldn't have to
> > be updated with each release?
>
> Automake does indeed offer such a mechanism (see "info automake doc texinfo"
> about 'version.texi'); even the truly ancient version newlib needs for
> --cygnus mode does.
>
> Newlib just doesn't use it.
Fixed manually for now.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-01-09 15:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-06 9:47 Wrong version displayed in documentation pdfs Freddie Chopin
2017-01-06 19:36 ` Hans-Bernhard Bröker
2017-01-09 15:23 ` Corinna Vinschen
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).