On 06/09/2016 21:01, Phil Race wrote:
FWIW "+1" from me since I just used/needed that patch to get my build to
continue on Solaris 11.3.
If you need it I have a jumbo patch that gets J9 to build on both S11.3
and S12. I'm working on splitting it up into individual patches and
getting them
FWIW "+1" from me since I just used/needed that patch to get my build to
continue on Solaris 11.3.
-phil.
On 9/6/2016 10:28 AM, Roger Riggs wrote:
Hi Alan,
Not a problem, I usually use mq to wrangle patches. (per repo)
Thanks, Roger
On 9/6/2016 1:25 PM, Alan Burlison wrote:
On 06/09/2016
Hi Alan,
Not a problem, I usually use mq to wrangle patches. (per repo)
Thanks, Roger
On 9/6/2016 1:25 PM, Alan Burlison wrote:
On 06/09/2016 18:10, Roger Riggs wrote:
ok, I will sponsor it.
Thanks.
(Usually the patches are relative to the repo being modified).
I can regen it if you
On 06/09/2016 18:10, Roger Riggs wrote:
ok, I will sponsor it.
Thanks.
(Usually the patches are relative to the repo being modified).
I can regen it if you want, I've been doing a lot of cross-repo patches
and have got into the habit of generating them from the topmost repo ;-)
--
Alan
ok, I will sponsor it.
(Usually the patches are relative to the repo being modified).
Thanks, Roger
On 9/6/2016 3:35 AM, Alan Burlison wrote:
On 01/09/2016 14:34, Alan Burlison wrote:
Changes looks good for me.
Thanks.
Could someone possibly sponsor this for me? I don't have commit
On 01/09/2016 14:34, Alan Burlison wrote:
Changes looks good for me.
Thanks.
Could someone possibly sponsor this for me? I don't have commit rights
yet...
Ping...
--
Alan Burlison
--
On 01/09/2016 14:31, Dmitry Samersoff wrote:
Changes looks good for me.
Thanks.
Could someone possibly sponsor this for me? I don't have commit rights
yet...
--
Alan Burlison
--
Alan,
Changes looks good for me.
-Dmitry
On 2016-08-31 14:55, Alan Burlison wrote:
> vfork(2) is deprecated on Solaris and using it generates compiler
> warnings. When compiled with warnings-as-errors, this results in
> compilation failures.
>
> Bug:
Martin,
Valid launch mechanisms for Solaris set in ProcessImpl.java as:
SOLARIS(LaunchMechanism.POSIX_SPAWN, LaunchMechanism.FORK),
So it's not possible to set VFORK as LaunchMechanism for Solaris.
and this fix doesn't change anything from customer perspective.
-Dmitry
On 2016-09-01 04:55,
On 01/09/2016 02:55, Martin Buchholz wrote:
Does an attempt to use vfork on Solaris result in something reasonable like
UnsupportedOperationException?
Yes:
$ jshell
| Welcome to JShell -- Version 9-internal
| For an introduction type: /help intro
jshell>
Does an attempt to use vfork on Solaris result in something reasonable like
UnsupportedOperationException?
On Wed, Aug 31, 2016 at 4:55 AM, Alan Burlison
wrote:
> vfork(2) is deprecated on Solaris and using it generates compiler
> warnings. When compiled with
vfork(2) is deprecated on Solaris and using it generates compiler
warnings. When compiled with warnings-as-errors, this results in
compilation failures.
Bug:https://bugs.openjdk.java.net/browse/JDK-8161360
Webrev: http://cr.openjdk.java.net/~alanbur/JDK-8161360
Thanks,
--
Alan Burlison
12 matches
Mail list logo