public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: David Smith <dsmith@redhat.com>
To: FOPA Leon constantin <leonconstantin.fopa@enseeiht.fr>,
	       Felix Lu <flu@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: trouble with installation of systemtap3-0 on Ubuntu 14.04
Date: Wed, 31 Aug 2016 14:03:00 -0000	[thread overview]
Message-ID: <ca387e28-277a-2cc5-1317-408e38de108a@redhat.com> (raw)
In-Reply-To: <7d8b765324c0e7c2f51e79140ae5999c@inp-toulouse.fr>

On 08/30/2016 11:20 PM, FOPA Leon constantin wrote:
> Hi Felix Hu,
> Hi David Smith,
> 
> removing libjson-c-dev was a good move.
> However I still get and error when I run make install.
> 
> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
>  restricted \write18 enabled.
> entering extended mode
> (/home/kamikague/Bureau/zombie/TTT/setups/systemtap-3.0/doc/tutorial.tex
> LaTeX2e <2011/06/27>
> Babel <3.9h> and hyphenation patterns for 78 languages loaded.
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> 
> ! LaTeX Error: File `html.sty' not found.

We could try to debug your documentation problems... but the easier
solution would be just to configure with '--disable-docs'. Then the
build system won't entry try to build the docs.

> It looks like something when wrong on documentation compilation.
> So I am not sure if the installation was successfull or not.
> 
> Additionally running ./stap on cache-hit-rate.stp(available here
> https://sourceware.org/systemtap/wiki/WSCacheHitRate)
> still rise error related to vfs and ioblock (see below). Can you help ?

I'm guessing that the installation wasn't successful, based on those
errors. Try reconfiguring without docs and try installing again. If you
still get the errors, we'll need to make sure you've got the right
kernel debuginfo installed.

-- 
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)

  reply	other threads:[~2016-08-31 14:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19  4:26 FOPA Leon constantin
2016-08-19 17:43 ` David Smith
2016-08-19 19:38 ` Felix Lu
2016-08-31  4:20   ` FOPA Leon constantin
2016-08-31 14:03     ` David Smith [this message]
2016-08-31 14:28       ` FOPA Leon constantin
2016-08-31 15:29     ` Frank Ch. Eigler
2017-01-26 11:17 Arkady
2017-01-26 17:43 ` David Smith
2017-01-26 19:39   ` Arkady
2017-01-26 20:40     ` David Smith
2017-01-26 20:55       ` Arkady
2017-01-26 21:25         ` David Smith
2017-01-27  6:07           ` Arkady
2017-01-27  9:01             ` Arkady
2017-01-27 15:22               ` David Smith
2017-01-27 16:00                 ` Arkady
2017-01-27 16:28                   ` David Smith
2017-01-27 18:02                     ` Arkady
2017-01-27 18:45                       ` David Smith
2017-01-27 19:43                         ` Arkady
2017-01-27 19:51                           ` Arkady
2017-01-27 20:13                             ` Arkady
2017-02-01 16:33                           ` Frank Ch. Eigler

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=ca387e28-277a-2cc5-1317-408e38de108a@redhat.com \
    --to=dsmith@redhat.com \
    --cc=flu@redhat.com \
    --cc=leonconstantin.fopa@enseeiht.fr \
    --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).