From: Nick Clifton <nickc@redhat.com>
To: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>,
binutils@sourceware.org
Subject: Re: [PATCH V4] gprofng: a new GNU profiler
Date: Fri, 4 Mar 2022 13:53:30 +0000 [thread overview]
Message-ID: <10dfd732-9930-22c6-6385-28aa41cd1816@redhat.com> (raw)
In-Reply-To: <b47455c9-5eac-b3cb-b7f8-dffb8ea4b1af@oracle.com>
Hi Vladimir,
> We have pushed these changes here:
> url: https://github.com/oracle/binutils-gdb.git/
> branch: oracle/gprofng-v4-1
OK, so using those sources, I built a set of the binutils binaries
without any special configuration options, ie:
configure -- quiet
and then I built gprofng and the other binutils tools. This worked
OK, but when I tried to run the gprofng testsuite only a few tests
appeared to run:
Running gprofng/testsuite/gprofng.display/display.exp ...
ERROR: compilation of test program in jsynprog failed
=== gprofng Summary ===
# of expected passes 14
# of unresolved testcases 1
Which does not look right. But then I remembered that I needed to
enable shared builds, so I tried:
configure --quiet --enable-shared
and this produced even worse test results:
Running gprofng/testsuite/gprofng.display/display.exp ...
ERROR: compilation of test program in jsynprog failed
ERROR: compilation of test program in mttest failed
ERROR: compilation of test program in mttest failed
ERROR: compilation of test program in mttest failed
ERROR: compilation of test program in mttest failed
ERROR: compilation of test program in mttest failed
ERROR: compilation of test program in mttest failed
ERROR: compilation of test program in mttest failed
ERROR: compilation of test program in synprog failed
ERROR: compilation of test program in synprog failed
ERROR: compilation of test program in synprog failed
ERROR: compilation of test program in synprog failed
ERROR: compilation of test program in synprog failed
ERROR: compilation of test program in synprog failed
ERROR: compilation of test program in synprog failed
=== gprofng Summary ===
# of unresolved testcases 15
The jsynprog and synprog failures is probably expected, since I do not
have the JDK installed, but the mttest compilation fails because I am
not testing an installed version of gprofng:
/dev/shm/delme/gprofng/gprofng/tmpdir/root/usr/local/bin/gprofng: error while loading shared libraries: libgprofng.so.0: cannot open shared object file: No such file or
directory
It would be really nice if I could test a built-but-not-installed
version of the sources....
Cheers
Nick
next prev parent reply other threads:[~2022-03-04 13:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fcc77804-0d0c-0f8e-5c3b-3ac034340b1a@oracle.com>
2021-11-03 18:05 ` Vladimir Mezentsev
2021-11-15 18:13 ` Ping: " Vladimir Mezentsev
2021-11-29 17:34 ` Vladimir Mezentsev
2021-12-10 9:38 ` Nick Clifton
2021-12-10 17:31 ` Vladimir Mezentsev
2021-12-13 15:13 ` Nick Clifton
2021-12-16 22:22 ` Vladimir Mezentsev
2022-01-12 0:48 ` Vladimir Mezentsev
2022-01-12 12:42 ` Nick Clifton
2022-01-12 15:17 ` Jose E. Marchesi
2022-01-12 15:23 ` Jose E. Marchesi
[not found] ` <c26c71b2-8cf1-2eef-206f-14c4774b2ba0@oracle.com>
2022-01-26 12:04 ` Nick Clifton
2022-01-26 17:10 ` Vladimir Mezentsev
2022-01-27 14:34 ` Jose E. Marchesi
2022-02-02 12:40 ` Maciej W. Rozycki
2022-02-02 16:30 ` Jose E. Marchesi
2022-02-03 6:23 ` Vladimir Mezentsev
2022-02-03 11:02 ` Maciej W. Rozycki
2022-02-03 12:16 ` Jose E. Marchesi
2022-03-02 19:47 ` Vladimir Mezentsev
2022-03-04 13:53 ` Nick Clifton [this message]
2022-03-07 21:42 ` Vladimir Mezentsev
2022-03-07 21:57 ` H.J. Lu
2022-03-07 22:25 ` Vladimir Mezentsev
2022-03-09 16:36 ` Nick Clifton
2022-03-09 21:13 ` Vladimir Mezentsev
2022-03-14 11:12 ` Martin Liška
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=10dfd732-9930-22c6-6385-28aa41cd1816@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=vladimir.mezentsev@oracle.com \
/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).