From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH V4] gprofng: a new GNU profiler
Date: Wed, 26 Jan 2022 09:10:06 -0800 [thread overview]
Message-ID: <1c976060-3d2f-1050-f948-9448acb33c71@oracle.com> (raw)
In-Reply-To: <eaa964f7-ab6d-38fe-6f5e-56289d04c46a@redhat.com>
Hi Nick,
On 1/26/22 04:04, Nick Clifton wrote:
> Hi Vladimir,
>
>> % tar tf mez.tar.gz
>> 0001-gprofng-add-the-gprofng-tool.patch
>> 0002-gprofng-add-testsuite-for-gprofng.patch
>> 0003-gprofng-add-the-gprofng-documentation.patch
>> 0004-gprofng-add-the-gprofng-build.patch
>
> Right - I am now testing these patches locally. I have however run
> into a possible issue. The patches apply cleanly and everything builds
> (although the configure script did mention that I do not have the JDK
> kit installed, which is true). But... when I run "make check" in the
> gprofng directory I get these results:
>
> % make check
> [...]
> Native configuration is x86_64-pc-linux-gnu
>
> === gprofng tests ===
>
> Schedule of variations:
> unix
>
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description
> file for target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file
> for target.
> Using
> /work/sources/binutils/current/gprofng/testsuite/config/default.exp as
> tool-and-target-specific interface file.
> Running
> /work/sources/binutils/current/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
>
> === gprofng Summary ===
>
> # of unresolved testcases 13
>
> Is this expected ?
It looks like you configured build without --enable-shared.
If yes, this is expected.
-Vladimir
> Is it something that I can ignore for now, or is there a test
> harness issue that needs to be resolved ?
>
> Cheers
> Nick
>
next prev parent reply other threads:[~2022-01-26 17:10 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 [this message]
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
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=1c976060-3d2f-1050-f948-9448acb33c71@oracle.com \
--to=vladimir.mezentsev@oracle.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).