From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, binutils@sourceware.org
Subject: Re: [PATCH] gprofng: Skip jsynprog with a broken javac
Date: Thu, 17 Mar 2022 10:11:05 -0700 [thread overview]
Message-ID: <44004a2d-4dbf-20ca-b90c-8e55189927e4@oracle.com> (raw)
In-Reply-To: <20220316135941.93773-1-hjl.tools@gmail.com>
Hi HJ,
Please check in your patch.
Thank you,
-Vladimir
On 3/16/22 06:59, H.J. Lu wrote:
> On CET enabled Linux/x86-64 machines, one can get
>
> $ javac simple.java
> Error: dl failure on line 894
> Error: failed /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.322.b06-6.fc35.x86_64/jre/lib/amd64/server/libjvm.so, because /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.322.b06-6.fc35.x86_64/jre/lib/amd64/server/libjvm.so: rebuild shared object with SHSTK support enabled
>
> Set GPROFNG_BROKEN_JAVAC to "yes" only with a broken javac and skip the
> jsynprog test with a broken javac.
>
> PR gprofng/28965
> * Makefile.am (GPROFNG_BROKEN_JAVAC): New.
> (check-DEJAGNU): Pass GPROFNG_BROKEN_JAVAC to runtest.
> * configure.ac (GPROFNG_BROKEN_JAVAC): New AC_SUBST. Set to yes
> with a broken javac.
> * Makefile.in: Regenerate.
> * configure: Likewise.
> * testsuite/gprofng.display/display.exp: Skip jsynprog with a
> broken javac.
> ---
> gprofng/Makefile.am | 2 ++
> gprofng/Makefile.in | 2 ++
> gprofng/configure | 27 +++++++++++++++++--
> gprofng/configure.ac | 17 ++++++++++++
> gprofng/testsuite/gprofng.display/display.exp | 8 +++++-
> 5 files changed, 53 insertions(+), 3 deletions(-)
prev parent reply other threads:[~2022-03-17 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 13:59 H.J. Lu
2022-03-17 17:11 ` Vladimir Mezentsev [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=44004a2d-4dbf-20ca-b90c-8e55189927e4@oracle.com \
--to=vladimir.mezentsev@oracle.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).