From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Building GDB 7.3.92 with MinGW
Date: Tue, 10 Jan 2012 20:56:00 -0000 [thread overview]
Message-ID: <83d3are0rn.fsf@gnu.org> (raw)
In-Reply-To: <CADPb22TAaiWxS-MjWZtpWutX9857hofz+k9zFCG+UFyExeaMyQ@mail.gmail.com>
> Date: Tue, 10 Jan 2012 10:46:24 -0800
> From: Doug Evans <dje@google.com>
> Cc: gdb-patches@sourceware.org
>
> > Â The reason is that gdb-cfg.texi and GDBvn.texi are not in the
> > Â tarball, but they are build dependencies of the manuals:
> >
> > Â Â GDB_DOC_BUILD_INCLUDES = \
> > Â Â Â Â Â Â gdb-cfg.texi \
> > Â Â Â Â Â Â GDBvn.texi
> > Â Â GDB_DOC_FILES = \
> > Â Â Â Â Â Â $(srcdir)/gdb.texinfo \
> > Â Â Â Â Â Â $(GDB_DOC_SOURCE_INCLUDES) \
> > Â Â Â Â Â Â $(GDB_DOC_BUILD_INCLUDES)
> > Â Â ...
> > Â Â # GDB MANUAL: info file
> > Â Â gdb.info: ${GDB_DOC_FILES}
> > Â Â Â Â Â Â $(MAKEINFO_CMD) $(READLINE_TEXI_INCFLAG) -I ${GDBMI_DIR} -I $(srcdir) \
> > Â Â Â Â Â Â Â Â Â Â -o gdb.info $(srcdir)/gdb.texinfo
> >
> > Â I think these two files should be added to the distribution, since
> > Â end users should not be required to have Texinfo installed to build
> > Â GDB.
>
> Sounds reasonable to me, but it seems odd.
> Why hasn't this come up before?
I have no idea. Maybe it's some remnant from the times, not so long
ago, when manuals weren't produced unless you said "make info".
> > As for standards.info, if we decide to keep distributing it (which I
> > don't think we should), we should at least make a point of having the
> > latest version in our tarballs; the one in 7.3.92 isn't.
>
> Minor preference for keeping it, I've gotten used to it being installed.
You can always get it from its origin, which is here:
http://www.gnu.org/prep/standards/standards.texi.tar.gz
next prev parent reply other threads:[~2012-01-10 20:55 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 18:46 Eli Zaretskii
2012-01-10 18:59 ` Doug Evans
2012-01-10 20:56 ` Eli Zaretskii [this message]
2012-01-13 11:28 ` Eli Zaretskii
2012-01-10 19:25 ` Tom Tromey
2012-01-10 20:55 ` Joseph S. Myers
2012-01-10 20:58 ` Eli Zaretskii
2012-01-10 21:00 ` Eli Zaretskii
2012-01-10 19:31 ` Alfred M. Szmidt
2012-01-10 21:01 ` Eli Zaretskii
2012-01-10 21:26 ` Doug Evans
2012-01-11 0:37 ` asmwarrior
2012-01-11 4:08 ` Eli Zaretskii
2012-01-11 4:54 ` asmwarrior
2012-01-11 17:54 ` Doug Evans
2012-01-12 0:17 ` asmwarrior
2012-01-12 6:47 ` Eli Zaretskii
2012-01-12 8:07 ` Joel Brobecker
2012-01-12 11:54 ` Eli Zaretskii
2012-01-12 12:35 ` Joel Brobecker
2012-01-12 16:59 ` Eli Zaretskii
2012-01-13 14:29 ` asmwarrior
2012-01-13 16:55 ` Eli Zaretskii
2012-01-14 13:53 ` asmwarrior
[not found] ` <4F117B33.8080906@gmail.com>
2012-01-14 18:15 ` Eli Zaretskii
2012-01-15 3:33 ` Pierre Muller
[not found] ` <18546.4176851839$1326580387@news.gmane.org>
2012-01-15 3:54 ` asmwarrior
[not found] ` <000001ccd30c$5ce854e0$16b8fea0$%muller@ics-cnrs.unistra.fr>
2012-01-15 13:35 ` Eli Zaretskii
2012-01-15 17:01 ` Joel Brobecker
2012-01-15 18:55 ` Eli Zaretskii
2012-01-15 18:01 ` Pierre Muller
[not found] ` <000301ccd3a7$3db8c460$b92a4d20$%muller@ics-cnrs.unistra.fr>
2012-01-15 18:55 ` Eli Zaretskii
2012-01-16 3:08 ` Pierre Muller
2012-01-10 21:33 ` Tom Tromey
2012-01-11 1:31 ` asmwarrior
2012-01-11 4:30 ` Eli Zaretskii
2012-01-11 4:30 ` asmwarrior
2012-01-11 3:32 ` Joel Brobecker
2012-01-13 11:06 ` Eli Zaretskii
2012-01-13 12:39 ` Joel Brobecker
2012-01-13 13:56 ` Eli Zaretskii
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=83d3are0rn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.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