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 regression on --with-system-readline
Date: Sat, 01 Jan 2011 09:23:00 -0000 [thread overview]
Message-ID: <8339pdq8la.fsf@gnu.org> (raw)
In-Reply-To: <20110101011319.GA27139@host1.dyn.jankratochvil.net>
> Date: Sat, 1 Jan 2011 02:13:24 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Tom Tromey <tromey@redhat.com>
>
> since:
> [2/2] RFA: --with-system-readline -vs- gdb.texinfo
> http://sourceware.org/ml/gdb-patches/2010-11/msg00270.html
>
> $ rm -rf gdb-7.2.50.20101231; tar xjf gdb-7.2.50.20101231.tar.bz2; cd gdb-7.2.50.20101231; CFLAGS= ./configure --with-system-readline; make; rm gdb/doc/gdb.info; make -C gdb/doc gdb.info
> ->
> [...]
> makeinfo -I ./../mi -I . \
> -o gdb.info ./gdb.texinfo
> ./gdb.texinfo:30521: @include `rluser.texi': No such file or directory.
> ./gdb.texinfo:30521: @include `inc-hist.texinfo': No such file or directory.
> [...]
> Fedora 14 x86_64
>
> It is because GDBvn.texi has started to depend on the configure options.
Aren't you supposed to "make distclean" whenever you reconfigure?
That's what I do in every project, because I don't trust the Makefiles
to DTRT in such case. E.g., what about all the *.o files you didn't
remove?
> -GDBvn.texi : ${gdbdir}/version.in
> +GDBvn.texi : ${gdbdir}/version.in Makefile
Thanks.
However, I don't like rules that depend of Makefiles, because they
tend to be re-run too much for no good reason. Note that this will
re-make the docs each time you reconfigure, even if you didn't change
the configuration.
But if I'm the only one who dislikes this, I won't object to the
change.
> Another issue is that GDBvn.texi and gdb-cfg.texi should not be distributed.
How can we not distribute them when gdb.texinfo @include's them, and
needs that for setting some of the variables the manual uses? If we
don't distribute them, end users will be unable to rebuild the manual.
What am I missing here?
next prev parent reply other threads:[~2011-01-01 9:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 1:13 Jan Kratochvil
2011-01-01 8:08 ` [patch] make info out-of-src-tree " Jan Kratochvil
2011-01-01 9:34 ` Eli Zaretskii
2011-01-01 10:51 ` Jan Kratochvil
2011-01-01 9:23 ` Eli Zaretskii [this message]
2011-01-01 9:38 ` [patch] make info " 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=8339pdq8la.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