public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@mips.com>
To: insight@sourceware.org
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: [PATCH] Support `make html' for plugins
Date: Thu, 26 Jul 2007 13:06:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61.0707261353570.9023@perivale.mips.com> (raw)

Hello,

 There is a problem with `make html' when issued from the gdb/ directory 
(used mainly to build some documentation in gdb/doc/) if the Insight 
subdirectory is present.  If this is the case, the command fails in 
gdb/gdbtk/plugins/:

make[4]: Entering directory `.../gdb/gdbtk/plugins'
Making html in rhabout
make[5]: Entering directory `.../gdb/gdbtk/plugins/rhabout'
make[5]: *** No rule to make target `html'.  Stop.
make[5]: Leaving directory `.../gdb/gdbtk/plugins/rhabout'
make[4]: *** [html-recursive] Error 1
make[4]: Leaving directory `.../gdb/gdbtk/plugins'

The reason is the template used for plugins is not automake-generated, so 
it has to supply the goal explicitly.

2007-07-26  Maciej W. Rozycki  <macro@mips.com>

	* Make-rules (html): Add goal.

 Applied as obvious.

  Maciej

gdbtk-plugins-html.diff
Index: gdb/src/gdb/gdbtk/plugins/Make-rules
===================================================================
--- gdb.orig/src/gdb/gdbtk/plugins/Make-rules	2007-07-26 13:32:46.000000000 +0100
+++ gdb/src/gdb/gdbtk/plugins/Make-rules	2007-07-26 13:46:53.000000000 +0100
@@ -112,6 +112,7 @@
 	    $(INSTALL_DATA) $(srcdir)/$$i $(libdir)/insight1.0/$(PLUGIN)/$$i ; \
 	done ;
 
+html:
 info:
 install-info:
 clean: $(CLEAN_TARGET)

             reply	other threads:[~2007-07-26 13:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 13:06 Maciej W. Rozycki [this message]
2007-07-26 14:39 ` Keith Seitz

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=Pine.LNX.4.61.0707261353570.9023@perivale.mips.com \
    --to=macro@mips.com \
    --cc=insight@sourceware.org \
    --cc=macro@linux-mips.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).