public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "ddstreet at canonical dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug documentation/27803] New: doc/SystemTap_Tapset_Reference/tapsets.pdf is removed during cleaning but not rebuilt
Date: Thu, 29 Apr 2021 22:26:19 +0000	[thread overview]
Message-ID: <bug-27803-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=27803

            Bug ID: 27803
           Summary: doc/SystemTap_Tapset_Reference/tapsets.pdf is removed
                    during cleaning but not rebuilt
           Product: systemtap
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: documentation
          Assignee: systemtap at sourceware dot org
          Reporter: ddstreet at canonical dot com
  Target Milestone: ---

The file "doc/SystemTap_Tapset_Reference/tapsets.pdf" is included in the make
target "clean-generic", since it's included in $CLEANFILES, along with
tapsets.xml

However, unlike tapsets.xml, there is no rule to remake this file, so after
cleaning the build will fail since tapsets.pdf doesn't exist.

It appears to be built from the scripts/update-docs script, but nothing in the
build actually calls that, that I can find.

Should tapsets.pdf get rebuild during the build, or should it be removed from
$CLEANFILES

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2021-04-29 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 22:26 ddstreet at canonical dot com [this message]
2023-12-06 21:42 ` [Bug documentation/27803] " wcohen at redhat dot com

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=bug-27803-6586@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).