All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Gerstner <mgerstner at suse.de>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2-tools man pages not installing?
Date: Tue, 03 Jul 2018 16:53:23 +0200	[thread overview]
Message-ID: <20180703145323.GA16483@f195.suse.de> (raw)
In-Reply-To: 3acb402299484e99a21524f88031fb51@AZDC-MMB02.GD-MS.US

[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]

Hello,

On Tue, Jul 03, 2018 at 01:46:14PM +0000, Scheie, Peter M wrote:
> When I build & install tpm2-tools, the man pages don't seem to get
> installed.  I'm just using the default './configure; make; sudo make
> install' routine, so everything is going into /usr/local/; therefore,
> I'd expect the man pages to end up in /usr/local/share/man, but they
> don't.  Do I need add an argument to configure to make that happen?

that is actually a bug and I addressed it via commit
72a28f36151db9bfa59a460ae0114dcece218862, however that commit didn't
make it into the current release.

So you either have to install them manually or, as a workaround, if you
have pandoc installed on the system, then the build system tries to
generate the man pages and alongside that also installs them.

Regards

Matthias

-- 
Matthias Gerstner <matthias.gerstner(a)suse.de>
Dipl.-Wirtsch.-Inf. (FH), Security Engineer
https://www.suse.com/security
Telefon: +49 911 740 53 290
GPG Key ID: 0x14C405C971923553

SUSE Linux GmbH
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nuernberg)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-07-03 14:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 14:53 Matthias Gerstner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-06 17:30 [tpm2] tpm2-tools man pages not installing? Scheie, Peter M
2018-07-06 17:12 Roberts, William C
2018-07-06 15:19 Scheie, Peter M
2018-07-06 14:10 Scheie, Peter M
2018-07-06 13:48 Joshua Lock
2018-07-05 20:44 Scheie, Peter M
2018-07-04 10:09 Joshua Lock
2018-07-03 17:49 Philip Tricca
2018-07-03 17:41 Scheie, Peter M
2018-07-03 13:46 Scheie, Peter M

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=20180703145323.GA16483@f195.suse.de \
    --to=tpm2@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.