From: Arkady <larytet@gmail.com>
To: David Smith <dsmith@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: trouble with installation of systemtap3-0 on Ubuntu 14.04
Date: Fri, 27 Jan 2017 20:13:00 -0000 [thread overview]
Message-ID: <CANA-60oVowdYGcLeQ6pY6i=k4mT37W=bmhpp0Sb8s5uCAP7PQw@mail.gmail.com> (raw)
In-Reply-To: <CANA-60rw=gANxy7aeWbkDbQxTRU6nW3M_fWedTK1zvT48fR4PQ@mail.gmail.com>
In my case I needed also to symlink json-c lib
ln -s /usr/local/lib/libjson-c.so.3.0.0 /usr/lib/x86_64-linux-gnu/libjson-c.so.3
On Fri, Jan 27, 2017 at 9:51 PM, Arkady <larytet@gmail.com> wrote:
> Sorry, it works. Recognizes the --monitor flag.
> Thank you!
>
> On Fri, Jan 27, 2017 at 9:42 PM, Arkady <larytet@gmail.com> wrote:
>> I have pulled the latest code
>>
>> commit 675838c2b2b97ca84ad6e561404426e7065da907
>> Author: David Smith <dsmith@redhat.com>
>> Date: Thu Jan 26 09:25:32 2017 -0600
>> Updated a comment in runtime/time.c.
>>
>> PKG_CONFIG=/usr/bin/pkg-config
>> ./configure --prefix=/home/arkady/systemtap/
>> reports that both json (I compiled and installed json from
>> https://github.com/json-c/json-c) and ncurses exist
>>
>>
>> make finishes fine and symbol HAVE_MONITOR_LIBS is defined
>>
>> $export PATH=/home/arkady/systemtap/bin:$PATH
>> $which stap
>> /home/arkady/systemtap/bin/stap
>> sudo stap --monitor -e 'probe begin { println("Hello World!"); }'
>> stap: unrecognized option '--monitor'
>> Try '--help' for more information.
>>
>> Still something is missing?
>>
>> On Fri, Jan 27, 2017 at 8:44 PM, David Smith <dsmith@redhat.com> wrote:
>>> OK, I think I know what is going on here. Release 3.0 doesn't include
>>> the latest 2 commits to staprun/Makefile.am. That's why you didn't have
>>> '-lpanel' in your link line.
>>>
>>> HEAD systemtap includes the following 2 commits that moved the json-c
>>> and ncurses libraries from AM_CFLAGS (causing them to appear too early
>>> in the link line) to stapio_LDADD (causing them to appear properly at
next prev parent reply other threads:[~2017-01-27 20:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2017-02-01 16:33 ` Frank Ch. Eigler
-- strict thread matches above, loose matches on Subject: below --
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
2016-08-31 14:28 ` FOPA Leon constantin
2016-08-31 15:29 ` 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='CANA-60oVowdYGcLeQ6pY6i=k4mT37W=bmhpp0Sb8s5uCAP7PQw@mail.gmail.com' \
--to=larytet@gmail.com \
--cc=dsmith@redhat.com \
--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).