From: Eli Zaretskii <eliz@gnu.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: install-html and install-pdf improvements
Date: Sat, 18 Apr 2009 07:31:00 -0000 [thread overview]
Message-ID: <83skk6ifjr.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0904171942570.12227@digraph.polyomino.org.uk>
> Date: Fri, 17 Apr 2009 19:48:57 +0000 (UTC)
> From: "Joseph S. Myers" <joseph@codesourcery.com>
> cc: gdb-patches@sourceware.org
>
> > > On Fri, 17 Apr 2009, Eli Zaretskii wrote:
> > >
> > > > Yes, but I don't understand why did you need to define docdir in
> > > > addition to pdfdir and htmldir. Unlike the other two, docdir is not
> > > > used anywhere, so why define it?
> > >
> > > The default definitions of htmldir and pdfdir use ${docdir}
> >
> > Sorry, I'm not following: what default definitions? These variables
> > are used neither in your patch nor in the current doc/Makefile.in.
> > What am I missing?
>
> The default definitions in the toplevel configure.ac, at least.
>
> docdir="\${datarootdir}/doc"
> pdfdir="\${docdir}"
> htmldir="\${docdir}"
That's okay, but I wasnt asking about the top level. What I was
asking about are these specific parts of the patch, which relate to
subdirectories, not to the top-level configure and Makefile.in:
Index: gdb/Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.1076
diff -u -r1.1076 Makefile.in
--- gdb/Makefile.in 30 Mar 2009 19:54:19 -0000 1.1076
+++ gdb/Makefile.in 17 Apr 2009 11:28:54 -0000
@@ -40,8 +40,10 @@
man8dir = $(mandir)/man8
man9dir = $(mandir)/man9
infodir = @infodir@
-pdfdir = $(prefix)/share/doc/gdb
-htmldir = $(prefix)/html
+datarootdir = @datarootdir@
+docdir = @docdir@
+htmldir = @htmldir@
+pdfdir = @pdfdir@
includedir = @includedir@
# This can be referenced by `LIBINTL' as computed by
@@ -530,6 +532,9 @@
"prefix=$(prefix)" \
"exec_prefix=$(exec_prefix)" \
"infodir=$(infodir)" \
+ "datarootdir=$(datarootdir)" \
+ "docdir=$(docdir)" \
+ "htmldir=$(htmldir)" \
"pdfdir=$(pdfdir)" \
"libdir=$(libdir)" \
"mandir=$(mandir)" \
Index: gdb/configure.ac
===================================================================
RCS file: /cvs/src/src/gdb/configure.ac,v
retrieving revision 1.92
diff -u -r1.92 configure.ac
--- gdb/configure.ac 15 Apr 2009 22:20:31 -0000 1.92
+++ gdb/configure.ac 17 Apr 2009 11:28:55 -0000
@@ -1955,6 +1955,12 @@
AC_DEFINE(GDB_DEFAULT_HOST_CHARSET, "UTF-8",
[Define to be a string naming the default host character set.])
+dnl Required by html, pdf, install-pdf and install-html
+AC_SUBST(datarootdir)
+AC_SUBST(docdir)
+AC_SUBST(htmldir)
+AC_SUBST(pdfdir)
+
AC_OUTPUT(Makefile .gdbinit:gdbinit.in gnulib/Makefile,
[
dnl Autoconf doesn't provide a mechanism for modifying definitions
Index: gdb/doc/configure.ac
===================================================================
RCS file: /cvs/src/src/gdb/doc/configure.ac,v
retrieving revision 1.2
diff -u -r1.2 configure.ac
--- gdb/doc/configure.ac 5 Jun 2008 22:36:56 -0000 1.2
+++ gdb/doc/configure.ac 17 Apr 2009 11:28:55 -0000
@@ -3,6 +3,11 @@
sinclude(../../config/acx.m4)
AC_PROG_INSTALL
AC_PROG_LN_S
+dnl Required by html, pdf, install-pdf and install-html
+AC_SUBST(datarootdir)
+AC_SUBST(docdir)
+AC_SUBST(htmldir)
+AC_SUBST(pdfdir)
ACX_PKGVERSION([GDB])
ACX_BUGURL([http://www.gnu.org/software/gdb/bugs/])
AC_OUTPUT(Makefile)
AFAICS, neither gdb/Makefile.in, nor anyone of the Makefile.in files
in its subdirectory, including gdb/doc/, uses $(docdir). So I'm
wondering why do we need a variable no one uses, and why do we pass it
to sub-Make?
IOW, why not just have $(htmldir) and $(pdfdir) in the Makefile's, and
let the top-level configure figure out where they should be, based on
"--with-*dir" switches? The sub-Make's would then get these values
from the variables we pass to them, and there's no need to compute
$(docdir) again in subdirectories. Note that, even according to your
patch, gdb/doc/Makefile.in does not define nor use $(docdir), only the
other two. I'm asking why can't we do the same in gdb/ as well?
next prev parent reply other threads:[~2009-04-18 7:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 11:47 Joseph S. Myers
2009-04-17 15:26 ` Eli Zaretskii
2009-04-17 15:30 ` Joseph S. Myers
2009-04-17 18:18 ` Eli Zaretskii
2009-04-17 19:43 ` Tom Tromey
2009-04-17 19:49 ` Joseph S. Myers
2009-04-18 7:31 ` Eli Zaretskii [this message]
2009-04-18 9:32 ` Joseph S. Myers
2009-04-20 19:51 ` Carlos O'Donell
2009-04-20 20:56 ` Eli Zaretskii
2009-04-21 12:45 ` Joseph S. Myers
2009-04-21 18:54 ` Eli Zaretskii
2009-04-17 15:58 ` Joseph S. Myers
2009-04-17 16:58 ` Tom Tromey
2009-04-17 17:31 ` Daniel Jacobowitz
2009-04-17 18:47 ` Tom Tromey
2009-04-17 19:16 ` 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=83skk6ifjr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.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