On 20/02/2014 11:22 PM, Magnus Ihse Bursie wrote:
During build, we create a touch file which is literally named '_the..'.
While cygwin handles this without issues, Windows believes this to be a
file with the extension "." and can't touch it, that is, not delete or
move it.
This patch renames thi
Hi,
The following is a preliminary webrev that allows OpenJDK to build and
run against a system-installed copy of lcms2 rather than the copy
bundled with OpenJDK:
root: http://cr.openjdk.java.net/~omajid/webrevs/system-lcms/00/
jdk: http://cr.openjdk.java.net/~omajid/webrevs/system-lcms/00-jdk/
On 2014-02-20 19:57, Mike Duigou wrote:
I've tried John's suggestion and it helps but is not enough. I believe I would
have to trap the outer make invocation as well. Unfortunately wrapping make in
a script just to be able to to use ctrl-\ is probably not worth it.
If what you need to wrap m
I've tried John's suggestion and it helps but is not enough. I believe I would
have to trap the outer make invocation as well. Unfortunately wrapping make in
a script just to be able to to use ctrl-\ is probably not worth it.
I'm instead using jstack though it can be harder to get timing right.
Hi Magnus:
During build, we create a touch file which is literally named
'_the..'. While cygwin handles this without issues, Windows believes
this to be a file with the extension "." and can't touch it, that is,
not delete or move it.
This patch renames this file (and others created at the s
Hi Omair,
Should I be pushing this to jdk9/dev ? (Or to jdk9/client?)
If you change client code, then the fix should go to the client repo to
avoid merge conflicts and allow for more manual testing prior to
integrating the changes into the master repo.
--
best regards,
Anthony
On 2/19/201
* Magnus Ihse Bursie [2014-02-20 05:35]:
> From my point of view, you can go either way. The changes are mostly
> in the build code, except for an include statement. But if the AWT
> folks feel more confident that way, sure, you can go via client.
Pushed:
http://hg.openjdk.java.net/jdk9/client/re
- Original Message -
> Hi Omair,
>
> > Should I be pushing this to jdk9/dev ? (Or to jdk9/client?)
>
> If you change client code, then the fix should go to the client repo to
> avoid merge conflicts and allow for more manual testing prior to
> integrating the changes into the master repo.
On 2014-02-13 22:27, Magnus Ihse Bursie wrote:
It turned out that it was not a good idea to line break AC_MSG_*
functions. :-( I didn't verify that properly before; my bad.
Here's a new-new review which restores the old long (but
properly-looking) AC_MSG lines.
(If you're curious, the line
During build, we create a touch file which is literally named '_the..'.
While cygwin handles this without issues, Windows believes this to be a
file with the extension "." and can't touch it, that is, not delete or
move it.
This patch renames this file (and others created at the same time) to
On 2014-02-20 09:47, Anthony Petrov wrote:
Hi Omair,
Should I be pushing this to jdk9/dev ? (Or to jdk9/client?)
If you change client code, then the fix should go to the client repo
to avoid merge conflicts and allow for more manual testing prior to
integrating the changes into the master r
11 matches
Mail list logo
