From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: [patch] make info out-of-src-tree regression on --with-system-readline
Date: Sat, 01 Jan 2011 09:34:00 -0000 [thread overview]
Message-ID: <831v4xq828.fsf@gnu.org> (raw)
In-Reply-To: <20110101080848.GA20595@host1.dyn.jankratochvil.net>
> Date: Sat, 1 Jan 2011 09:08:48 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Tom Tromey <tromey@redhat.com>
>
> On Sat, 01 Jan 2011 02:13:24 +0100, Jan Kratochvil wrote:
> > Another issue is that GDBvn.texi and gdb-cfg.texi should not be distributed.
> > But that bug is a different one on top of this bug. That bug of a needless
> > files distribution is dependent on magic GDB `make dist' I do not know and
> > also that dist bug is not serious enough.
>
> This part has a real consequence - the previous patch does not apply for build
> trees out of the src tree. It may be even a makeinfo bug.
>
> The change below is not needed for texi2dvi. In fact it even breaks it.
Can't you repair it by a suitable setting of TEXINPUTS?
> Another possibility is to error out if $(srcdir)/GDBvn.texi exists so that no
> disambiguities may exist. GDBvn.texi would have to be removed from the
> distributed tars.
What are the problems with not distributing it in the tarball, again?
(I take back my questions in the previous mail.)
> gdb.info: ${GDB_DOC_FILES}
> $(MAKEINFO) $(READLINE_TEXI_INCFLAG) -I ${GDBMI_DIR} -I $(srcdir) \
> - -o gdb.info $(srcdir)/gdb.texinfo
> + -o gdb.info gdb.texinfo
If we put "-I ." _before_ "-I $(srcdir)", doesn't it solve the issue
more nicely?
next prev parent reply other threads:[~2011-01-01 9:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 1:13 [patch] make info " Jan Kratochvil
2011-01-01 8:08 ` [patch] make info out-of-src-tree " Jan Kratochvil
2011-01-01 9:34 ` Eli Zaretskii [this message]
2011-01-01 10:51 ` Jan Kratochvil
2011-01-01 9:23 ` [patch] make info " Eli Zaretskii
2011-01-01 9:38 ` Jan Kratochvil
2011-01-01 10:00 ` Eli Zaretskii
2011-01-01 11:16 ` Jan Kratochvil
2011-01-01 11:26 ` Eli Zaretskii
2011-01-01 11:43 ` Jan Kratochvil
2011-01-01 12:20 ` Eli Zaretskii
2011-01-01 12:30 ` Jan Kratochvil
2011-01-01 15:36 ` Eli Zaretskii
2011-01-01 16:32 ` Jan Kratochvil
2011-01-01 16:44 ` Eli Zaretskii
2011-01-03 12:21 ` [new patch] " Jan Kratochvil
2011-01-03 12:57 ` Eli Zaretskii
2011-01-03 13:02 ` Jan Kratochvil
2011-01-04 5:43 ` Jan Kratochvil
2011-01-04 6:31 ` Eli Zaretskii
2011-01-01 11:40 ` [patch] " Jan Kratochvil
2011-01-01 12:15 ` 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=831v4xq828.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@redhat.com \
/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