From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 82027 invoked by alias); 31 Aug 2016 04:20:27 -0000 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org Received: (qmail 82017 invoked by uid 89); 31 Aug 2016 04:20:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.2 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 spammy=H*r:Debian-9.4, rise, H*r:8.14.3, Lon X-HELO: inpsmtp.inp-toulouse.fr Received: from inpsmtp.inp-toulouse.fr (HELO inpsmtp.inp-toulouse.fr) (193.48.203.41) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 31 Aug 2016 04:20:16 +0000 Received: from imap.inp-toulouse.fr (imap.inp-toulouse.fr [193.48.203.40]) by inpsmtp.inp-toulouse.fr (8.14.3/8.14.3/Debian-9.4) with ESMTP id u7V4K6aO001951; Wed, 31 Aug 2016 06:20:07 +0200 Received: from rcmail.inp-toulouse.fr (rcmail.inp-toulouse.fr [193.48.203.51]) by imap.inp-toulouse.fr (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id u7V4K4NN012788; Wed, 31 Aug 2016 06:20:06 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Wed, 31 Aug 2016 04:20:00 -0000 From: FOPA Leon constantin To: Felix Lu , Cc: Subject: Re: trouble with installation of systemtap3-0 on Ubuntu 14.04 In-Reply-To: <86033635.71503982.1471635464483.JavaMail.zimbra@redhat.com> References: <86033635.71503982.1471635464483.JavaMail.zimbra@redhat.com> Message-ID: <7d8b765324c0e7c2f51e79140ae5999c@inp-toulouse.fr> X-Sender: leonconstantin.fopa@enseeiht.fr User-Agent: INP Webmail X-SW-Source: 2016-q3/txt/msg00217.txt.bz2 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. Type X to quit or to proceed, or enter new name. (Default extension: sty) Enter file name: X dvips -t letter -o tutorial.ps tutorial.dvi This is dvips(k) 5.993 Copyright 2013 Radical Eye Software (www.radicaleye.com) dvips: DVI file can't be opened: tutorial.dvi: No such file or directory make[3]: *** [tutorial.ps] Erreur 1 make[3]: quittant le répertoire « /home/kamikague/Bureau/zombie/TTT/setups/systemtap-3.0/doc » make[2]: *** [all-recursive] Erreur 1 make[2]: quittant le répertoire « /home/kamikague/Bureau/zombie/TTT/setups/systemtap-3.0/doc » make[1]: *** [all-recursive] Erreur 1 make[1]: quittant le répertoire « /home/kamikague/Bureau/zombie/TTT/setups/systemtap-3.0 » make: *** [all] Erreur 2 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 ? Best regards, and thanks for you time, Fopa Léon Constantin root@prt-sepia03:/home/kamikague/Bureau/zombie/TTT/setups/systemtap-3.0# ./stap -v ../../scripts/systemtap/cache-hit-rate.stp Pass 1: parsed user script and 0 library scripts using 45856virt/13048res/4488shr/8888data kb, in 0usr/0sys/0real ms. semantic error: while resolving probe point: identifier 'vfs' at ../../scripts/systemtap/cache-hit-rate.stp:3:7 source: probe vfs.read { ^ semantic error: probe point mismatch (similar: procfs, end, never, perf, begin): identifier 'vfs' at :3:7 source: probe vfs.read { ^ semantic error: while resolving probe point: identifier 'ioblock' at :9:7 source: probe ioblock.request { ^ semantic error: probe point mismatch (similar: begin, end, procfs, error, kprobe): identifier 'ioblock' at :9:7 source: probe ioblock.request { ^ Pass 2: analyzed script: 3 probes, 0 functions, 0 embeds, 5 globals using 45856virt/13048res/4488shr/8888data kb, in 0usr/0sys/0real ms. Pass 2: analysis failed. [man error::pass2] On Fri, 19 Aug 2016 15:37:44 -0400 (EDT), Felix Lu wrote: > Hi, > > > ----- Original Message ----- >> From: "FOPA Leon constantin" >> To: systemtap@sourceware.org >> Sent: Friday, 19 August, 2016 12:26:33 AM >> Subject: trouble with installation of systemtap3-0 on Ubuntu 14.04 >> >> Hi you all, >> >> I use to install systemtap simply as: >> >> apt-get install systemtap >> >> But I get and error while testing the cache-hit-rate.stp from the >> systemtap wiki. >> >> >> root@prt-sepia03:/home/kamikague/Bureau/zombie/TTT/scripts/systemtap# >> stap cache-hit-rate.stp >> semantic error: unable to find member 'bi_size' for struct bio >> (alternatives: bi_next bi_bdev bi_flags bi_rw bi_iter >> bi_phys_segments >> bi_seg_front_size bi_seg_back_size bi_remaining bi_end_io bi_private >> bi_ioc bi_css bi_integrity bi_vcnt bi_max_vecs bi_cnt bi_io_vec >> bi_pool >> bi_inline_vecs): operator '->' at >> /usr/share/systemtap/tapset/linux/ioblock.stp:113:20 >> source: size = $bio->bi_size >> ^ >> >> Pass 2: analysis failed. [man error::pass2] >> Tip: /usr/share/doc/systemtap/README.Debian should help you get >> started. >> >> The error look like it was fixed in the latest version of systemTap. >> So >> I uninstall the systemtap package to start all over again with a >> fresh >> installation >> from source code. I downloaded the latest version of >> systemtap-3.0.tar.gz (here >> http://fossies.org/linux/misc/systemtap-3.0.tar.gz/) >> and I get the following error output when trying to install it (see >> below). >> >> it seems that libjson is not referenced accurately, I confirm that >> libjson is on its latest version on my system. >> > > I have just tested this on Ubuntu 14.04 and was able to reproduce > this error. > As David mentioned, removing libjson-c is probably the easiest > workaround. This > was recently fixed in the latest git version of systemtap if you > would like to > go for the alternative approach of not removing libjson-c.