[PATCH V4] gprofng: a new GNU profiler

[Vladimir Mezentsev]

   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
>