Sorry I'm so slow in responding to this...
The primary reason for the special case on Windows is the unreliability
and slowness of the network connections.
Builds using a local jdk vs. a J:/ mapped can be 5 hours long when
they might normally be 1hr or less. These just come from reports I
have
Adding a sanity check warning about J:/ usage would be a nice addition
to this change.
-kto
Jonathan Gibbons wrote:
Kelly,
Perhaps make sanity on Windows could give a warning about the use
of network paths, if such is detected.
-- Jon
Kelly O'Hair wrote:
Sorry I'm so slow in responding to
On 4/23/2009 10:15 PM Kelly O'Hair wrote:
The primary reason for the special case on Windows is the unreliability
and slowness of the network connections.
Builds using a local jdk vs. a J:/ mapped can be 5 hours long when
they might normally be 1hr or less. These just come from reports I
have
Jon, Kelly,
Then what about the default builds on Linux/Solaris that do use the
/java share and do not issue any warning message? I agree that these
builds are generally much faster than on Windows, but still. Besides, as
I mentioned before, on my local systems the /java directory and the J:
Anthony,
On pretty much any system you can tell if a drive is local or not,
albeit in a system specific way.
-- Jon
Anthony Petrov wrote:
Jon, Kelly,
Then what about the default builds on Linux/Solaris that do use the
/java share and do not issue any warning message? I agree that these
This sanity check would be a nice to have thing, but it it can't
be done in a simple way I'm not sure I want to see a bunch of convoluted
logic added, we have too much of that already :^(
And it does go beyond your intended change. Maybe a separate bug for
another time, like a sanity warnings on
Hello,
Back in 2007 we already discussed this issue with Kelly, but
transitioning to Mercurial just stopped the work. So, I would like to
revive this now.
Here's a part of the output generated by `grep -r BOOTDIR make/*`:
make/common/shared/Defs-solaris.gmk: _BOOTDIR1
