GNU bug report logs -
#36921
texinfo: @setfilename is not mandatory
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 36921 in the body.
You can then email your comments to 36921 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-automake <at> gnu.org
:
bug#36921
; Package
automake
.
(Sun, 04 Aug 2019 13:24:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Дилян Палаузов <dilyan.palauzov <at> aegee.org>
:
New bug report received and forwarded. Copy sent to
bug-automake <at> gnu.org
.
(Sun, 04 Aug 2019 13:24:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello,
I have a .texi file and in Makefile.am:
info_TEXINFOS = doc/z.texi
Running autoreconf -visf emits:
configure.ac:13: installing './compile'
configure.ac:7: installing './missing'
Makefile.am: installing './depcomp'
Makefile.am: error: './doc/z.texi' missing @setfilename
autoreconf: automake failed with exit status: 1
I have texinfo (or rather makeinfo) 6.6 and automake 1.16.1 (most likely installed from most recent git).
The texinfo manual says in node @setfilename:
“ When a '@setfilename' line is present, the Texinfo processors ignore
everything written before the '@setfilename' line. This is why the very
first line of the file (the '\input' line) does not show up in the
output.
. . .
'@setfilename' used to be required by the Texinfo processors, and
some other programs may still expect it to be present; for example,
Automake (*note (automake)Texinfo::).”
Please adjust automake to come forward, when @setfilename is missing, implying the default value.
Regards
Dilyan
Information forwarded
to
bug-automake <at> gnu.org
:
bug#36921
; Package
automake
.
(Fri, 16 Aug 2019 10:10:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 36921 <at> debbugs.gnu.org (full text, mbox):
On Sun, Aug 04, 2019 at 01:22:34PM +0000, Дилян Палаузов wrote:
> Hello,
>
> I have a .texi file and in Makefile.am:
>
> info_TEXINFOS = doc/z.texi
>
> Running autoreconf -visf emits:
>
> configure.ac:13: installing './compile'
> configure.ac:7: installing './missing'
> Makefile.am: installing './depcomp'
> Makefile.am: error: './doc/z.texi' missing @setfilename
> autoreconf: automake failed with exit status: 1
>
> I have texinfo (or rather makeinfo) 6.6 and automake 1.16.1 (most likely installed from most recent git).
>
> The texinfo manual says in node @setfilename:
>
> “ When a '@setfilename' line is present, the Texinfo processors ignore
> everything written before the '@setfilename' line. This is why the very
> first line of the file (the '\input' line) does not show up in the
> output.
>
> . . .
> '@setfilename' used to be required by the Texinfo processors, and
> some other programs may still expect it to be present; for example,
> Automake (*note (automake)Texinfo::).”
>
> Please adjust automake to come forward, when @setfilename is missing, implying the default value.
>
I posted a patch to fix this issue:
https://lists.gnu.org/archive/html/bug-automake/2019-01/msg00002.html
Hopefully somebody will have time to apply it. I am not sure how
actively Automake is being developed at the moment.
Information forwarded
to
bug-automake <at> gnu.org
:
bug#36921
; Package
automake
.
(Mon, 19 Aug 2019 17:03:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 36921 <at> debbugs.gnu.org (full text, mbox):
I posted a patch to fix this issue:
https://lists.gnu.org/archive/html/bug-automake/2019-01/msg00002.html
Thanks Gavin. I hope Jim (Meyering) or I will install the patch soon,
although the timing of the next release is unknown at this point.
I'm just starting to get a grip on the development side of automake;
just trying to help since Jim doesn't have a lot of time right now and
all other am developers seem to have disappeared. (If you yourself have
any time/interest, help is greatly needed!) --best, karl.
Information forwarded
to
bug-automake <at> gnu.org
:
bug#36921
; Package
automake
.
(Mon, 02 Sep 2019 17:28:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 36921 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Gavin Smith proposed a patch for this back in http://bugs.gnu.org/34201
Another reference to the problem: http://bugs.gnu.org/36921
In the attached (in Gavin's name), I've added a NEWS entry and
adjusted the ChangeLog entry. Will push in a day or so if no comment.
[automake-relax-setfilename.diff (application/octet-stream, attachment)]
Information forwarded
to
bug-automake <at> gnu.org
:
bug#36921
; Package
automake
.
(Tue, 03 Sep 2019 07:55:03 GMT)
Full text and
rfc822 format available.
Message #17 received at 36921 <at> debbugs.gnu.org (full text, mbox):
Hello Jim,
Jim Meyering <jim <at> meyering.net> writes:
> Gavin Smith proposed a patch for this back in http://bugs.gnu.org/34201
> Another reference to the problem: http://bugs.gnu.org/36921
>
> In the attached (in Gavin's name), I've added a NEWS entry and
> adjusted the ChangeLog entry. Will push in a day or so if no comment.
Thanks for taking care of this. :-)
> From 309a6c477eec80b847078699303c65ccd7787eb0 Mon Sep 17 00:00:00 2001
> From: Gavin Smith <gavinsmith0123 <at> gmail.com>
> Date: Sun, 25 Aug 2019 21:07:58 -0700
> Subject: [PATCH] automake: do not require @setfilename in Texinfo files
>
> Texinfo no longer requires a @setfilename directive in each
> .texi file, so automake now also relaxes its restriction.
> * bin/automake.in (scan_texinfo_file): Derive name of info file from
> name of input file if no @setfilename line occurs in the file.
> * t/txinfo-no-setfilename.sh: New test.
> * t/list-of-tests.mk: Add it.
> * NEWS: Mention it.
>
> Fixes automake bugs #36921 and #34201.
> ---
Not really important but HACKING <Writing a good commit message>
recommends a slightly different style.
--8<---------------cut here---------------start------------->8---
topic: brief description (this is the "summary line")
<reference to relevant bugs, if any>
Here goes a more detailed explanation of why the commit is needed,
and a general overview of what it does, and how. This section
should almost always be provided, possibly only with the expection
of obvious fixes or very trivial changes.
And if the detailed explanation is quite long or detailed, you can
want to break it in more paragraphs.
Then you can add references to relevant mailing list discussions
(if any), with proper links. But don't take this as an excuse for
writing incomplete commit messages! The "distilled" conclusions
reached in such discussions should have been placed in the
paragraphs above.
Finally, here you can thank people that motivated or helped the
change. So, thanks to John Doe for bringing up the issue, and to
J. Random Hacker for providing suggestions and testing the patch.
<detailed list of touched files>
--8<---------------cut here---------------end--------------->8---
--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
Information forwarded
to
bug-automake <at> gnu.org
:
bug#36921
; Package
automake
.
(Sat, 14 Sep 2019 12:36:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 36921 <at> debbugs.gnu.org (full text, mbox):
On Mon, Sep 2, 2019 at 6:28 PM Jim Meyering <jim <at> meyering.net> wrote:
>
> Gavin Smith proposed a patch for this back in http://bugs.gnu.org/34201
> Another reference to the problem: http://bugs.gnu.org/36921
>
> In the attached (in Gavin's name), I've added a NEWS entry and
> adjusted the ChangeLog entry. Will push in a day or so if no comment.
Thanks for taking the time to look at this.
Information forwarded
to
bug-automake <at> gnu.org
:
bug#36921
; Package
automake
.
(Sun, 15 Sep 2019 16:58:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 36921 <at> debbugs.gnu.org (full text, mbox):
On Sat, Sep 14, 2019 at 5:35 AM Gavin Smith <gavinsmith0123 <at> gmail.com> wrote:
> On Mon, Sep 2, 2019 at 6:28 PM Jim Meyering <jim <at> meyering.net> wrote:
> >
> > Gavin Smith proposed a patch for this back in http://bugs.gnu.org/34201
> > Another reference to the problem: http://bugs.gnu.org/36921
> >
> > In the attached (in Gavin's name), I've added a NEWS entry and
> > adjusted the ChangeLog entry. Will push in a day or so if no comment.
>
> Thanks for taking the time to look at this.
Oh! Thanks for the reminder. I've just pushed that.
Reply sent
to
Karl Berry <karl <at> freefriends.org>
:
You have taken responsibility.
(Sat, 11 Jan 2025 21:47:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Дилян Палаузов <dilyan.palauzov <at> aegee.org>
:
bug acknowledged by developer.
(Sat, 11 Jan 2025 21:47:02 GMT)
Full text and
rfc822 format available.
Message #28 received at 36921-done <at> debbugs.gnu.org (full text, mbox):
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 09 Feb 2025 12:24:07 GMT)
Full text and
rfc822 format available.
This bug report was last modified 32 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.