I saw this on a new Solaris/x86 box that was provisioned by our internal
IT about recently. It is in use by our team and is not part of the JPRT
infrastructure.
So I am worried that anyone starting hotspot development on their own
Solaris 10 box would be baffled by the same issue.
I will send the review request to hotspot-runtime-dev instead.
Thanks
- Ioi
On 08/01/2013 04:16 PM, David Holmes wrote:
Hi Ioi,
I don't recall that this was x86 specific. I'm not sure this is with
doing as this is the first sighting in a few years. I'm more
interested in getting the machine fixed and knowing how it came to be
configured that way.
Plus this really needs to go through hotspot-runtime-dev as the change
is in hotspot.
David
On 2/08/2013 3:26 AM, Ioi Lam wrote:
|Please review a very small fix:||
||
||http://cr.openjdk.java.net/~iklam/8022093/solaris_dtrace_001/||
||
||Bug: syntax error near "umpiconninfo_t" -- when building on Solaris
10/X86||
||
||http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8022093||
|| https://jbs.oracle.com/bugs/browse/JDK-8022093||
||
||Summary of fix:||
||
|| Added more error messages to show possible workaround:||
||
||---vvv---||
||dtrace: failed to compile script dtrace.d: "/usr/lib/dtrace/mpi.d",
line 68: syntax error near "umpiconninfo_t"||
||*****************************************************************||
||* If you are seeing 'syntax error near "umpiconninfo_t"' on Solaris||
||* 10/X86, try doing 'cd /usr/lib/dtrace && gzip mpi.d' as root, ||
||* or set the environment variable HOTSPOT_DISABLE_DTRACE_PROBES||
||* to disable dtrace probes for this build.||
||*****************************************************************||
||---^^^---||
||
||Tests:||
||
|| JPRT||
||
||Thanks||
||- Ioi|
