From: Josh Stone <jistone@redhat.com>
To: systemtap@sourceware.org
Subject: Re: Build local systemtap
Date: Tue, 16 Apr 2013 19:06:00 -0000 [thread overview]
Message-ID: <516DA10E.7010206@redhat.com> (raw)
In-Reply-To: <CAPTDLfGE+96B1-3UtbmXZtoGU3nx2JQQPDf=-o7p_3s6J2_GCw@mail.gmail.com>
On 04/16/2013 11:42 AM, Kalai Rajah N wrote:
> Can I build systemtap with binutils instead of elfutils?
No, the two are only similar in the programs they provide, but we use
libraries that are only in elfutils (especially libdw).
> I got the recent snapshot of systemtap and built it with the
> following command
>
> ../systemtap-20130413/configure --prefix=${PREFIX} --libdir=${PREFIX}/lib64
> --with-elfutils=/dev/shm/sw-build/elfutils-0.155
>
> make & make install went through fine.
Ok, when using "--with-elfutils" it should build and install private
copies of those elfutils libraries. Are they successfully installed in
$libdir/systemtap/ ?
>
> But, when I run stap --help, I get the following error. Going through
> systemtap release notes, I found that it needs elfutils and not
> binutils. Is this there a way to substitute binutils for elfutils? Or
> can I have both elfutils and binutils on the samesystem?
>
> stap: /usr/lib64/libelf.so.1: version `ELFUTILS_1.5' not found
> (required by stap)
> stap: /usr/lib64/libdw.so.1: version `ELFUTILS_0.148' not found
> (required by stap)
> stap: /usr/lib64/libdw.so.1: version `ELFUTILS_0.138' not found
> (required by stap)
> stap: /usr/lib64/libdw.so.1: version `ELFUTILS_0.142' not found
> (required by stap)
> stap: /usr/lib64/libdw.so.1: version `ELFUTILS_0.143' not found
> (required by stap)
> stap: /usr/lib64/libdw.so.1: version `ELFUTILS_0.149' not found
> (required by stap)
This is clearly picking up the system's older version of elfutils, which
lacks the necessary symbols you built against. So after you verify that
stap's private elfutils installed correctly, please check if "eu-readelf
-d stap" contains the right RPATH/RUNPATH.
It might also be an issue if the prefix you chose was a relative path.
I'm not sure if we translate that to a full path at build time.
prev parent reply other threads:[~2013-04-16 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 18:42 Kalai Rajah N
2013-04-16 19:06 ` Josh Stone [this message]
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=516DA10E.7010206@redhat.com \
--to=jistone@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).