Re: Is anyone able to build on Win 7
This sounds very interesting. I have no experience with MinGW/MSYS, but will most definitely start looking into it asap and see how hard it would be to get the new build compatible with it. /Erik On 2012-03-08 19:00, Volker Simonis wrote: This thread will probably never end (Windows 2046 :) So I did more test.. - I wanted to compare with MKS and the first thing I hit on was a bug in MKS's 9.4 version of cpio (CFS# 32408--- cpio can not handle files which are ReadOnly). And it's expensive and installation and license handling is PITA if you use several virtual machiines.. - Still couldn't find the reason why the build hangs with Cygwin 1.7.10 Finally I decided to try something new - MinGW/MSYS. And indeed - it worked, it's nearly as fast as MKS, it can use the default make which comes with the MinGW/Installation. Read the glory details at: http://mail.openjdk.java.net/pipermail/build-dev/2012-March/005729.html Please feel free to test, review and (hopfully) submit it. The changes are intentionally against the old, traditional build system to fix the mentioned Cygwin problems and simplify the Windows build just now. As next steps I see the following points: - integrate MinGW/MSYS with the new build system - completely remove nmake from the HotSpot build and use prallel GNU make like on Linux (I know this works and that it's faster - just have to build a OpenJDK patch) Any comments? Volker
Re: Is anyone able to build on Win 7
Volker, Thank you for amazing work! Just a curious: 1. Do you have any performance numbers for hotspot built with MinGW? Is it as fast as one built with MS VC? 2. Did you see any issues with third-party JNI code? Thank you! -Dmitry On 2012-03-08 22:00, Volker Simonis wrote: This thread will probably never end (Windows 2046 :) So I did more test.. - I wanted to compare with MKS and the first thing I hit on was a bug in MKS's 9.4 version of cpio (CFS# 32408--- cpio can not handle files which are ReadOnly). And it's expensive and installation and license handling is PITA if you use several virtual machiines.. - Still couldn't find the reason why the build hangs with Cygwin 1.7.10 Finally I decided to try something new - MinGW/MSYS. And indeed - it worked, it's nearly as fast as MKS, it can use the default make which comes with the MinGW/Installation. Read the glory details at: http://mail.openjdk.java.net/pipermail/build-dev/2012-March/005729.html Please feel free to test, review and (hopfully) submit it. The changes are intentionally against the old, traditional build system to fix the mentioned Cygwin problems and simplify the Windows build just now. As next steps I see the following points: - integrate MinGW/MSYS with the new build system - completely remove nmake from the HotSpot build and use prallel GNU make like on Linux (I know this works and that it's faster - just have to build a OpenJDK patch) Any comments? Volker On Wed, Feb 15, 2012 at 1:10 PM, Fredrik Öhrström fredrik.ohrst...@oracle.com wrote: - kelly.oh...@oracle.com skrev: So I'm with you on the stat() theory, makes a great deal of sense. The stat theory is very interesting, but it is unclear to me if it explains all of the problem. I setup a quadruple boot x86_64 machine with 4GB of ram and 4 cores: Winxp 32bit Win7 64bit Solaris 64bit Ubuntu 64bit And tested the build times on the different OS:es. Ubuntu Fastest by far. Solaris, slower, but this is only because of bad CC performance. Winxp, even slower but still ok. Win7, ridiculously slow. The configure script prints one line per second! Clearly, just running a bash script in cygwin/win7/64bit is problematic. If we get 10% speedup from dash, then that is not going to help because the slowdown is a factor 10. Could someone try out the difference between a 32bit win7 clean install and a 64 bit win7 clean install when running the latest cygwin and just the build-infra/jdk8/common/autoconf/configure script? (My patience for installing many OSes into the same box, just ran out. And virtualization testing can give a hint, but cannot be entirely trusted.) //Fredrik -- Dmitry Samersoff Java Hotspot development team, SPB04 * There will come soft rains ...
Re: Is anyone able to build on Win 7
Hi Dimitry, I I haven't build the HotSpot with MinGW - that would be a completely different project. I've just used the MinGW/MSYS environment (i.e. shell, make, various Unix-tools) to build the OpenJDK. The build still uses MSVC as compiler. Building the HotSpot with the GCC from MinGW should be possible with a combination of the current Windows makefiles and the gcc compiler settings from the linux makefiles although it would require quiet a bit of hacking. I'm not so sure however if the whole JDK could be build with GCC from MinGW because I'm not sure if MinGW has include files and wrappers for all the required Windows libraries - but honestly speaking I havn't looked into it until now. Regards, Volker On Fri, Mar 9, 2012 at 10:06 AM, Dmitry Samersoff dmitry.samers...@oracle.com wrote: Volker, Thank you for amazing work! Just a curious: 1. Do you have any performance numbers for hotspot built with MinGW? Is it as fast as one built with MS VC? 2. Did you see any issues with third-party JNI code? Thank you! -Dmitry On 2012-03-08 22:00, Volker Simonis wrote: This thread will probably never end (Windows 2046 :) So I did more test.. - I wanted to compare with MKS and the first thing I hit on was a bug in MKS's 9.4 version of cpio (CFS# 32408--- cpio can not handle files which are ReadOnly). And it's expensive and installation and license handling is PITA if you use several virtual machiines.. - Still couldn't find the reason why the build hangs with Cygwin 1.7.10 Finally I decided to try something new - MinGW/MSYS. And indeed - it worked, it's nearly as fast as MKS, it can use the default make which comes with the MinGW/Installation. Read the glory details at: http://mail.openjdk.java.net/pipermail/build-dev/2012-March/005729.html Please feel free to test, review and (hopfully) submit it. The changes are intentionally against the old, traditional build system to fix the mentioned Cygwin problems and simplify the Windows build just now. As next steps I see the following points: - integrate MinGW/MSYS with the new build system - completely remove nmake from the HotSpot build and use prallel GNU make like on Linux (I know this works and that it's faster - just have to build a OpenJDK patch) Any comments? Volker On Wed, Feb 15, 2012 at 1:10 PM, Fredrik Öhrström fredrik.ohrst...@oracle.com wrote: - kelly.oh...@oracle.com skrev: So I'm with you on the stat() theory, makes a great deal of sense. The stat theory is very interesting, but it is unclear to me if it explains all of the problem. I setup a quadruple boot x86_64 machine with 4GB of ram and 4 cores: Winxp 32bit Win7 64bit Solaris 64bit Ubuntu 64bit And tested the build times on the different OS:es. Ubuntu Fastest by far. Solaris, slower, but this is only because of bad CC performance. Winxp, even slower but still ok. Win7, ridiculously slow. The configure script prints one line per second! Clearly, just running a bash script in cygwin/win7/64bit is problematic. If we get 10% speedup from dash, then that is not going to help because the slowdown is a factor 10. Could someone try out the difference between a 32bit win7 clean install and a 64 bit win7 clean install when running the latest cygwin and just the build-infra/jdk8/common/autoconf/configure script? (My patience for installing many OSes into the same box, just ran out. And virtualization testing can give a hint, but cannot be entirely trusted.) //Fredrik -- Dmitry Samersoff Java Hotspot development team, SPB04 * There will come soft rains ...
Re: Is anyone able to build on Win 7
On Thu, Mar 8, 2012 at 8:00 PM, Kelly O'Hair kelly.oh...@oracle.com wrote: On Mar 8, 2012, at 10:00 AM, Volker Simonis wrote: This thread will probably never end (Windows 2046 :) So I did more test.. - I wanted to compare with MKS and the first thing I hit on was a bug in MKS's 9.4 version of cpio (CFS# 32408--- cpio can not handle files which are ReadOnly). And it's expensive and installation and license handling is PITA if you use several virtual machiines.. MKS 9.4 is seriously broken for us. I use 9.0p3 or 9.0p4. I filed a ticket with MKS on this issue months ago and have never heard back from them, and we have a support contract with them too. :^( - Still couldn't find the reason why the build hangs with Cygwin 1.7.10 that's a new one for me. When both MKS and CYGWIN are installed on the same system it can be tricky. After I install MKS I usually go in and take MKS out of the default PATH, and change SHELL to be just /usr/bin/sh (which appears to be more of a universal keyword than a path to a shell). Then I go shut down and disable all MKS services. Then when I want an MKS shell started up, I have some hacky PATH setting and exec of the MKS shell. I could send you the formula if you would like. I've just kept wishing MKS could go away for us... someday... And you have provide a light at the end of the tunnel. ;^) Thanks! Finally I decided to try something new - MinGW/MSYS. And indeed - it worked, it's nearly as fast as MKS, it can use the default make which comes with the MinGW/Installation. Read the glory details at: http://mail.openjdk.java.net/pipermail/build-dev/2012-March/005729.html Please feel free to test, review and (hopfully) submit it. The changes are intentionally against the old, traditional build system to fix the mentioned Cygwin problems and simplify the Windows build just now. As next steps I see the following points: - integrate MinGW/MSYS with the new build system - completely remove nmake from the HotSpot build and use prallel GNU make like on Linux (I know this works and that it's faster - just have to build a OpenJDK patch) Any comments? Fantastic stuff. I'll work on getting it in place. On replacing NMAKE, I agree with you however, I think NMAKE may be in cahoots with the VS compiler with regards to licensing checks or pre-compiled headers, the build is pretty fast. In my crude attempts in the past, I could never get anywhere close to the NMAKE build speed. Never completely understood why. :^( I don't understand the licensing checks problem you mention? Do you mean 'cl' can only be called from nmake? I havn't seen this problem, although our internal build without 'nmake' I was mentioning runs with the commercial and not the Express version of MSVS. For the precompiled headers issue we found a solution. I'll just have to port it to the OpenJDK. -kto Volker On Wed, Feb 15, 2012 at 1:10 PM, Fredrik Öhrström fredrik.ohrst...@oracle.com wrote: - kelly.oh...@oracle.com skrev: So I'm with you on the stat() theory, makes a great deal of sense. The stat theory is very interesting, but it is unclear to me if it explains all of the problem. I setup a quadruple boot x86_64 machine with 4GB of ram and 4 cores: Winxp 32bit Win7 64bit Solaris 64bit Ubuntu 64bit And tested the build times on the different OS:es. Ubuntu Fastest by far. Solaris, slower, but this is only because of bad CC performance. Winxp, even slower but still ok. Win7, ridiculously slow. The configure script prints one line per second! Clearly, just running a bash script in cygwin/win7/64bit is problematic. If we get 10% speedup from dash, then that is not going to help because the slowdown is a factor 10. Could someone try out the difference between a 32bit win7 clean install and a 64 bit win7 clean install when running the latest cygwin and just the build-infra/jdk8/common/autoconf/configure script? (My patience for installing many OSes into the same box, just ran out. And virtualization testing can give a hint, but cannot be entirely trusted.) //Fredrik
Re: Is anyone able to build on Win 7
An interesting tidbit... I was talking to the JavaFX RE team which does builds on Windows XP and Windows 2003 X64. They have always used CYGWIN for builds, but there isn't many Makefiles used on Windows, it's mostly Ant scripts. So CYGWIN is used but probably not a major player. No MKS was ever used. Both windows builds had been the long pole, maybe 2 hours each, and past experiments showed that using physical hardware rather than VMware virtual machines could reduce the builds to about 1hour. So we knew that VMs would cost us, but assumed that as we got faster hosts this would improve. After McAfee was installed, the Windows XP builds went down the toilet, but the Windows X64 builds were not impacted as much. Apparently the policies in place for Windows XP (considered a desktop environment) are considerably different from that of Windows 2003 (considered a server environment). Another... I now have 3 Windows 7 X64 systems I can now use to test jdk8 builds. I built the entire openjdk8 (hotspot included, product only) in slightly under an hour, just the Windows 64bit product. This is a VMware VM on a fully loaded X4170M2 system hosting just 6 VMs, each VM has 4 vCPUs with lots of RAM. This was using MKS 9.0p4 I can use it to do some additional experiments on Volker's changes, but it will take me a little time. -kto On Feb 15, 2012, at 4:10 AM, Fredrik Öhrström wrote: - kelly.oh...@oracle.com skrev: So I'm with you on the stat() theory, makes a great deal of sense. The stat theory is very interesting, but it is unclear to me if it explains all of the problem. I setup a quadruple boot x86_64 machine with 4GB of ram and 4 cores: Winxp 32bit Win7 64bit Solaris 64bit Ubuntu 64bit And tested the build times on the different OS:es. Ubuntu Fastest by far. Solaris, slower, but this is only because of bad CC performance. Winxp, even slower but still ok. Win7, ridiculously slow. The configure script prints one line per second! Clearly, just running a bash script in cygwin/win7/64bit is problematic. If we get 10% speedup from dash, then that is not going to help because the slowdown is a factor 10. Could someone try out the difference between a 32bit win7 clean install and a 64 bit win7 clean install when running the latest cygwin and just the build-infra/jdk8/common/autoconf/configure script? (My patience for installing many OSes into the same box, just ran out. And virtualization testing can give a hint, but cannot be entirely trusted.) //Fredrik
Re: Is anyone able to build on Win 7
- kelly.oh...@oracle.com skrev: So I'm with you on the stat() theory, makes a great deal of sense. The stat theory is very interesting, but it is unclear to me if it explains all of the problem. I setup a quadruple boot x86_64 machine with 4GB of ram and 4 cores: Winxp 32bit Win7 64bit Solaris 64bit Ubuntu 64bit And tested the build times on the different OS:es. Ubuntu Fastest by far. Solaris, slower, but this is only because of bad CC performance. Winxp, even slower but still ok. Win7, ridiculously slow. The configure script prints one line per second! Clearly, just running a bash script in cygwin/win7/64bit is problematic. If we get 10% speedup from dash, then that is not going to help because the slowdown is a factor 10. Could someone try out the difference between a 32bit win7 clean install and a 64 bit win7 clean install when running the latest cygwin and just the build-infra/jdk8/common/autoconf/configure script? (My patience for installing many OSes into the same box, just ran out. And virtualization testing can give a hint, but cannot be entirely trusted.) //Fredrik
Re: Is anyone able to build on Win 7
.
Official builds are still happening on Windows XP and Windows 2003 X64 and
these
problems are not being seen on those systems yet...
although we recently have been visited by the McAfee plague so maybe it's
just a matter of time. ;^(
Someone with some strong Windows experience needs to run this to ground.
We do need this to work, eventually.
-kto
On Jan 25, 2012, at 9:09 AM, Pete Brunet wrote:
I started W7 in safe mode and the build failed with a fork failure. I
think that eliminates things in the BLODA list. If anyone out there is
building OK on W7 please send your configuration, e.g. as shown below.
Maybe that will suggest a different version of cygwin or bash. -Pete
On 1/25/12 9:55 AM, Pete Brunet wrote:
Thanks Volker, I was thinking I'm going to have to try using XP in a
VM. My W7 config is very close to yours (make 3.81 instead of 3.82).
W7 Pro, 64 bit, SP1
Intel Core 2 Duo, P8700, 2.53 GHz, 8 GB RAM
CYGWIN_NT-6.1-WOW64 Bevo 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
GNU bash, version 4.1.10(4)-release (i686-pc-cygwin)
GNU Make 3.81
Pete
On 1/25/12 9:06 AM, Volker Simonis wrote:
Hi Peter,
glad to see that other have the same problems:)
But seriously, on Windows 7 I'm currently experiencing the same
massive build problems and I'm not sure what the root cause of these
problems is.
I found the following bug which exactly describes the problems I'm
facing:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6903517
Among others, these are:
- rm: cannot remove directory `META-INF': Directory not empty
- error: cannot create example2.html: Permission denied
- [javac]
C:\Software\OpenJDK\jdk8\langtools\src\share\classes\com\sun\tools\javac\util\SharedNameTable.java:40:
error: error while writing SharedNameTable:
c:\Software\OpenJDK\output_amd64\langtools\build\bootstrap\classes\com\sun\tools\javac\util\SharedNameTable.class
(Access is denied)
but I also saw the 'out of memory' and 'for' problems mentioned by you.
The description of bug 6903517 references the Big List of Dodgy Apps
(http://cygwin.com/faq/faq.using.html#faq.using.bloda). This is a list
in the Cygwin FAQ which lists applications like Virus Scanners which
can interfere with Cygwin in an unpredictable way. An indeed the
Windows 7 box on which I observe the problems has some of them
installed (e.g. McAffe {Agent, GTI Proxy Agent, Intrusion Prevention,
VirusScan Enterprise, AntySpywaare Enterprise} to name just a few).
On the other hand, on the same Windows 7 box I have a virtual machine
running inside VirtualBox with WindowsXP which has the same McAffe
software installed and it is running without any problems. The OpenJDK
build always succeeds in the virtual machine!
So I'm not quite sure of this is:
- a problem of some additional software which is running on my Windows
7 box and interferes with Cygwin
- a general Windows7 problem
- a problem of the specific Cygwin version I'm using
- a problem of Cygwin running on 64-bit Windows 7
I'll try to further narrow down the problem, but of course any hints
are highly welcome (unfortunately I can't easily get rid of the McAffe
stuff without losing my job, so please don't advise this:)
Regards,
Volker
PS: below you can find the exact versions of the software/hardware I'm
using:
64-bit Windows 7, SP 1
Dual Core Intel i7, 8GB RAM
Cygwin (output of uname -a):
CYGWIN_NT-6.1-WOW64 WDFN00299915A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686
Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
In the Virtual box VM I have the following system:
64-bit Windows XP Professional Version 2003 SP 2
Cygwin (output of uname -a):
CYGWIN_NT-5.2-WOW64 WDFV00248216A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686
Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
On Tue, Jan 24, 2012 at 5:52 PM, Pete Brunet peter.bru...@oracle.com
wrote:
Is anyone able to build on Win 7? I'm on my 8th build hoping to get to
the end and have seen these errors:
out of memory, 3 times - I have more than enough memory
fork: Resource temporarily unavailable, 3 times
error 126, once
I have read http://cygwin.com/faq-nochunks.html#faq.using.bloda so
apparently something on my system is causing a problem but I haven't
been successful in finding it yet. I have my Norton 360 Auto-Protect
turned off. It would be helpful to know if anyone has successfully
built on Win 7 and also if anyone has ideas on what I might look for
beyond what is listed in the cygwin FAQ.
Thanks, Pete
Re: Is anyone able to build on Win 7
2012-02-14 12:29, Volker Simonis skrev:
To cut a long story short:
- disabling on access scanning of *.{java,c,cpp,h,hpp} seems to
resolve the file io problems (permission denied, access denied)
- disabling ASLR seems to resolve the fork problems
Great work! Do you know if disabling ASLR affects the fork performance
on 64 bit windows?
//Fredrik
Re: Is anyone able to build on Win 7
On Tue, Feb 14, 2012 at 12:43 PM, Fredrik Öhrström
fredrik.ohrst...@oracle.com wrote:
2012-02-14 12:29, Volker Simonis skrev:
To cut a long story short:
- disabling on access scanning of *.{java,c,cpp,h,hpp} seems to
resolve the file io problems (permission denied, access denied)
- disabling ASLR seems to resolve the fork problems
Great work! Do you know if disabling ASLR affects the fork performance
on 64 bit windows?
No, definitely not.
The build time on my DualCore i7 @ 2.7 GHz notebook with 8GB Ram is
constantly 1h43min for a full JDK8 opt build.
Now that that the build seems stable I want to compare it with a Linux
build in a VirtualBox VM on the same host.
I'll let you know the results once I'm done, but I don't think that
fork is the big problem - at least not the only one.
But once you asked here's my main suspect since long time (you asked
so you have to read the conspiracy:)
stat (or lstat/fstat/stat64 ...)
-
I'm quite sure that the poor implementation of stat in Cygwin and its
usage in make is one of the main reasons
why the build Windows build is so terrible slow in Windows compared to Linux.
I first realized this years ago when I was first building Windows
inside a VMWare image with the sources on
network shares. The build times were excessively long and it was not
the compile times because SMB shares
do a quite efficient caching - it was the times which make needed in
order to check the build dependencies.
The build times could be improved by factors if the sources were moved
to a local disc.
But even locallly, I think that the stat calls for large dependency
lists as we have them in the OpenJDK build
may still be one of the causes for the slow build. Running make inside
strace will reveal the shear number
of these calls and there is evidence that the stat performance is
really poor in Cygwin.
I'll attach some unsorted links to some of the resources which discuss
this issue just in case somebody wants to
deep dive into this topic. I'm definitely not a Windows/Cygwin expert
and I can't promise I'll have the time
to solve it 'real soon' but I'll definitely stick to this topic
because it is a real PITA (especially if you want to
change your build from MKS to Cygwin the developers who will first
love you because freed them from of
the MKS licensing night mare will very soon kill you because of the
build times:)
performance issue with cgywin make
http://www.mail-archive.com/make-w32@gnu.org/msg01353.html
- mailing list thread which compares the bad performance of Cygwin
make with MS nmake and discusses
how some of the problems have been solved in CMake by using direct
windows sys-calls instead of stat.
make 3.82 performing more stat() calls than 3.81
http://lists.gnu.org/archive/html/bug-make/2011-09/msg00025.html
- mailing list thread discussing a bug in make 3.82 which leads to
even more calls to stat
(and has been fixed already in the head revision of make)
Cygwin Performance and stat()
http://omgili.com/mailinglist/cygwin/cygwin/com/efe8a37b2e4466daa7b6eb1aa610c3d7squirrelebmailwingertorg.html
- very long thrad, very ‘flamy’, no outcome, some interesting infos nevertheless
cygwin: Use native Win32 API for stat
http://marc.info/?l=gitm=122278284210941
- partial patch for the problem by implementing a stripped down
version of stat which does just enough...
_NutFastStat(), _NutFastStat64()
http://www.mkssoftware.com/docs/man3/_NutFastStat.3.asp
- MKSs limited but faster version of stat (not sure if MKS make uses
this, but that may be an
explanation why builds under MKS are reported to be considerably
faster compared to Cygwin builds
Managing Projects with GNU Make, 3rd Edition, The Power of GNU make
for Building Anything, By Robert Mecklenburg
http://shop.oreilly.com/product/9780596006105.do
- Chapter 10: Improving the Performance of make freely available as
PDF download:
http://reilly.com/catalog/make3/book/ch10.pdf
Compile time Local Cygwin vs. VMware session on same system
http://cygwin.com/ml/cygwin/2008-10/threads.html#00415
- mail thread suggesting the usage of ‘dash’ instead of ‘bash’ for a
10% performance improvement
//Fredrik
Re: Is anyone able to build on Win 7
Fantastic information set. Many thanks for all this digging.
I suspect, that our build infrastructure work may help, in that if we get rid
of the nested makes,
then I can only assume we will be doing fewer stat() calls, but I think we
still have a problem.
A year or so ago, I managed to reduce the fork/exec count by 50% thinking it
would improve windows
build times, it did very little, I was disappointed, and assumed the bigger
spike had to be related to I/O.
So I tried a fast SSD on a Windows machine, which sure made it quiet, but also
didn't help much.
So I'm with you on the stat() theory, makes a great deal of sense.
-kto
On Feb 14, 2012, at 6:59 AM, Volker Simonis wrote:
On Tue, Feb 14, 2012 at 12:43 PM, Fredrik Öhrström
fredrik.ohrst...@oracle.com wrote:
2012-02-14 12:29, Volker Simonis skrev:
To cut a long story short:
- disabling on access scanning of *.{java,c,cpp,h,hpp} seems to
resolve the file io problems (permission denied, access denied)
- disabling ASLR seems to resolve the fork problems
Great work! Do you know if disabling ASLR affects the fork performance
on 64 bit windows?
No, definitely not.
The build time on my DualCore i7 @ 2.7 GHz notebook with 8GB Ram is
constantly 1h43min for a full JDK8 opt build.
Now that that the build seems stable I want to compare it with a Linux
build in a VirtualBox VM on the same host.
I'll let you know the results once I'm done, but I don't think that
fork is the big problem - at least not the only one.
But once you asked here's my main suspect since long time (you asked
so you have to read the conspiracy:)
stat (or lstat/fstat/stat64 ...)
-
I'm quite sure that the poor implementation of stat in Cygwin and its
usage in make is one of the main reasons
why the build Windows build is so terrible slow in Windows compared to Linux.
I first realized this years ago when I was first building Windows
inside a VMWare image with the sources on
network shares. The build times were excessively long and it was not
the compile times because SMB shares
do a quite efficient caching - it was the times which make needed in
order to check the build dependencies.
The build times could be improved by factors if the sources were moved
to a local disc.
But even locallly, I think that the stat calls for large dependency
lists as we have them in the OpenJDK build
may still be one of the causes for the slow build. Running make inside
strace will reveal the shear number
of these calls and there is evidence that the stat performance is
really poor in Cygwin.
I'll attach some unsorted links to some of the resources which discuss
this issue just in case somebody wants to
deep dive into this topic. I'm definitely not a Windows/Cygwin expert
and I can't promise I'll have the time
to solve it 'real soon' but I'll definitely stick to this topic
because it is a real PITA (especially if you want to
change your build from MKS to Cygwin the developers who will first
love you because freed them from of
the MKS licensing night mare will very soon kill you because of the
build times:)
performance issue with cgywin make
http://www.mail-archive.com/make-w32@gnu.org/msg01353.html
- mailing list thread which compares the bad performance of Cygwin
make with MS nmake and discusses
how some of the problems have been solved in CMake by using direct
windows sys-calls instead of stat.
make 3.82 performing more stat() calls than 3.81
http://lists.gnu.org/archive/html/bug-make/2011-09/msg00025.html
- mailing list thread discussing a bug in make 3.82 which leads to
even more calls to stat
(and has been fixed already in the head revision of make)
Cygwin Performance and stat()
http://omgili.com/mailinglist/cygwin/cygwin/com/efe8a37b2e4466daa7b6eb1aa610c3d7squirrelebmailwingertorg.html
- very long thrad, very ‘flamy’, no outcome, some interesting infos
nevertheless
cygwin: Use native Win32 API for stat
http://marc.info/?l=gitm=122278284210941
- partial patch for the problem by implementing a stripped down
version of stat which does just enough...
_NutFastStat(), _NutFastStat64()
http://www.mkssoftware.com/docs/man3/_NutFastStat.3.asp
- MKSs limited but faster version of stat (not sure if MKS make uses
this, but that may be an
explanation why builds under MKS are reported to be considerably
faster compared to Cygwin builds
Managing Projects with GNU Make, 3rd Edition, The Power of GNU make
for Building Anything, By Robert Mecklenburg
http://shop.oreilly.com/product/9780596006105.do
- Chapter 10: Improving the Performance of make freely available as
PDF download:
http://reilly.com/catalog/make3/book/ch10.pdf
Compile time Local Cygwin vs. VMware session on same system
http://cygwin.com/ml/cygwin/2008-10/threads.html#00415
- mail thread suggesting the usage of ‘dash’ instead of ‘bash’ for a
10% performance improvement
//Fredrik
Re: Is anyone able to build on Win 7
2012-02-02 00:10, Kelly O'Hair skrev: I don't know what the current state is. The CYGWIN community seemed pretty adamant that they wanted to stamp out all drive letter pathnames. As I understood it, it's not so much the version of make.exe, but how the make.exe was built. Some kind of 'allow drive letter paths' option needs to be turned on when building. I created a neat solution to get around this drive letter problem in the new build-infra/jdk8 (jdk7) forest. The configure script compiles an executable called uncygdrive.exe The make variables that point to tools that do not understand /cygdrive paths, like CC:=cl.exe and JAVA:=java.exe are rewritten to: CC:=uncygdrive.exe cl.exe JAVA:=uncygdrive.exe java.exe As you can guess, the uncygdrive command parses the command line and rewrites any /cygdrive/c/ into just c:/ (likewise for any other drive letter). It even enters into @files and creates a temporary file with adjusted content. Then it execs the new adjusted command line. Works great and the Makefiles become much simpler since you can just use /cygdrive everywhere! A more important problem is the dreaded slowdown of cygwin on 64 bit windows. It is believed to be the fork simulation gone haywaire when dealing with 64 bit address space, but what do I know. //Fredrik
Re: Is anyone able to build on Win 7
Does this article provide any help:
https://kc.mcafee.com/corporate/index?page=contentid=KB55075actp=searchviewlocale=en_USsearchid=1328818133782
It suggests that rebase'ing the CYGWIN DLL's will help. Seems a bit strange to
me, just passing it on.
-kto
On Jan 25, 2012, at 5:10 PM, Pete Brunet wrote:
I just had success with the following changes:
- downgraded from cygwin 1.7.9 (with bash 4.1.10) to 1.7.0 (with bash
3.2.49)
- changed ...\jdk\make\docs\Makefile line 74
ifeq ($(ARCH_DATA_MODEL),64)
MAX_VM_MEMORY = 1024
else
MAX_VM_MEMORY = 1024 --- This was 512
endif
I've only done one build and in prior builds had other issues besides
the memory problem, i.e. fork and error 126, but there's always hope.
If others could report their W7 configurations and whether or not there
were problems, that would be helpful.
Pete
On 1/25/12 6:17 PM, Kelly O'Hair wrote:
Sorry guys, I don't have the time or priority to track this down.
Official builds are still happening on Windows XP and Windows 2003 X64 and
these
problems are not being seen on those systems yet...
although we recently have been visited by the McAfee plague so maybe it's
just a matter of time. ;^(
Someone with some strong Windows experience needs to run this to ground.
We do need this to work, eventually.
-kto
On Jan 25, 2012, at 9:09 AM, Pete Brunet wrote:
I started W7 in safe mode and the build failed with a fork failure. I
think that eliminates things in the BLODA list. If anyone out there is
building OK on W7 please send your configuration, e.g. as shown below.
Maybe that will suggest a different version of cygwin or bash. -Pete
On 1/25/12 9:55 AM, Pete Brunet wrote:
Thanks Volker, I was thinking I'm going to have to try using XP in a
VM. My W7 config is very close to yours (make 3.81 instead of 3.82).
W7 Pro, 64 bit, SP1
Intel Core 2 Duo, P8700, 2.53 GHz, 8 GB RAM
CYGWIN_NT-6.1-WOW64 Bevo 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
GNU bash, version 4.1.10(4)-release (i686-pc-cygwin)
GNU Make 3.81
Pete
On 1/25/12 9:06 AM, Volker Simonis wrote:
Hi Peter,
glad to see that other have the same problems:)
But seriously, on Windows 7 I'm currently experiencing the same
massive build problems and I'm not sure what the root cause of these
problems is.
I found the following bug which exactly describes the problems I'm facing:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6903517
Among others, these are:
- rm: cannot remove directory `META-INF': Directory not empty
- error: cannot create example2.html: Permission denied
- [javac]
C:\Software\OpenJDK\jdk8\langtools\src\share\classes\com\sun\tools\javac\util\SharedNameTable.java:40:
error: error while writing SharedNameTable:
c:\Software\OpenJDK\output_amd64\langtools\build\bootstrap\classes\com\sun\tools\javac\util\SharedNameTable.class
(Access is denied)
but I also saw the 'out of memory' and 'for' problems mentioned by you.
The description of bug 6903517 references the Big List of Dodgy Apps
(http://cygwin.com/faq/faq.using.html#faq.using.bloda). This is a list
in the Cygwin FAQ which lists applications like Virus Scanners which
can interfere with Cygwin in an unpredictable way. An indeed the
Windows 7 box on which I observe the problems has some of them
installed (e.g. McAffe {Agent, GTI Proxy Agent, Intrusion Prevention,
VirusScan Enterprise, AntySpywaare Enterprise} to name just a few).
On the other hand, on the same Windows 7 box I have a virtual machine
running inside VirtualBox with WindowsXP which has the same McAffe
software installed and it is running without any problems. The OpenJDK
build always succeeds in the virtual machine!
So I'm not quite sure of this is:
- a problem of some additional software which is running on my Windows
7 box and interferes with Cygwin
- a general Windows7 problem
- a problem of the specific Cygwin version I'm using
- a problem of Cygwin running on 64-bit Windows 7
I'll try to further narrow down the problem, but of course any hints
are highly welcome (unfortunately I can't easily get rid of the McAffe
stuff without losing my job, so please don't advise this:)
Regards,
Volker
PS: below you can find the exact versions of the software/hardware I'm
using:
64-bit Windows 7, SP 1
Dual Core Intel i7, 8GB RAM
Cygwin (output of uname -a):
CYGWIN_NT-6.1-WOW64 WDFN00299915A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686
Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
In the Virtual box VM I have the following system:
64-bit Windows XP Professional Version 2003 SP 2
Cygwin (output of uname -a):
CYGWIN_NT-5.2-WOW64 WDFV00248216A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686
Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
On Tue, Jan 24, 2012 at 5:52 PM, Pete Brunet peter.bru...@oracle.com
wrote:
Is anyone able to build
Re: Is anyone able to build on Win 7
On Feb 2, 2012, at 5:22 AM, Fredrik Öhrström wrote: 2012-02-02 00:10, Kelly O'Hair skrev: I don't know what the current state is. The CYGWIN community seemed pretty adamant that they wanted to stamp out all drive letter pathnames. As I understood it, it's not so much the version of make.exe, but how the make.exe was built. Some kind of 'allow drive letter paths' option needs to be turned on when building. I created a neat solution to get around this drive letter problem in the new build-infra/jdk8 (jdk7) forest. The configure script compiles an executable called uncygdrive.exe The make variables that point to tools that do not understand /cygdrive paths, like CC:=cl.exe and JAVA:=java.exe are rewritten to: CC:=uncygdrive.exe cl.exe JAVA:=uncygdrive.exe java.exe As you can guess, the uncygdrive command parses the command line and rewrites any /cygdrive/c/ into just c:/ (likewise for any other drive letter). It even enters into @files and creates a temporary file with adjusted content. Then it execs the new adjusted command line. Works great and the Makefiles become much simpler since you can just use /cygdrive everywhere! Excellent. This assumes that the CYGWIN user has not used mount points, e.g. mount C:/foobar to /foobar but we can deal with that when the time comes. I like your solution. A more important problem is the dreaded slowdown of cygwin on 64 bit windows. It is believed to be the fork simulation gone haywaire when dealing with 64 bit address space, but what do I know. Yeah. It's bad enough that it could be slower because it is a VM, could be slowed down by AV On-Access scanning, or is just a slow Windows file system. So many things can slow a Windows system down. :^( And my long term plan was to do both 32bit and 64bit builds on Windows 64bit so we need fewer systems, and we use 64bit OS's that can have more CPU and RAM for scaling up the build. :^( If we had a really good Windows System Performance expert somewhere out there, I bet he/she could find some ways for us to make this Windows X64 CYGWIN situation faster. I'm not that person, and I've run out of ideas. :^( In the meantime I'm still using MKS. :^( -kto //Fredrik
Re: Is anyone able to build on Win 7
- a problem of Cygwin running on 64-bit Windows 7 I'll try to further narrow down the problem, but of course any hints are highly welcome (unfortunately I can't easily get rid of the McAffe stuff without losing my job, so please don't advise this:) Regards, Volker PS: below you can find the exact versions of the software/hardware I'm using: 64-bit Windows 7, SP 1 Dual Core Intel i7, 8GB RAM Cygwin (output of uname -a): CYGWIN_NT-6.1-WOW64 WDFN00299915A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin bash 4.1.10(4) // installed by Cygwin setup.exe make 3.82 // compiled by myself In the Virtual box VM I have the following system: 64-bit Windows XP Professional Version 2003 SP 2 Cygwin (output of uname -a): CYGWIN_NT-5.2-WOW64 WDFV00248216A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin bash 4.1.10(4) // installed by Cygwin setup.exe make 3.82 // compiled by myself On Tue, Jan 24, 2012 at 5:52 PM, Pete Brunet peter.bru...@oracle.com wrote: Is anyone able to build on Win 7? I'm on my 8th build hoping to get to the end and have seen these errors: out of memory, 3 times - I have more than enough memory fork: Resource temporarily unavailable, 3 times error 126, once I have read http://cygwin.com/faq-nochunks.html#faq.using.bloda so apparently something on my system is causing a problem but I haven't been successful in finding it yet. I have my Norton 360 Auto-Protect turned off. It would be helpful to know if anyone has successfully built on Win 7 and also if anyone has ideas on what I might look for beyond what is listed in the cygwin FAQ. Thanks, Pete
Re: Is anyone able to build on Win 7
can interfere with Cygwin in an unpredictable way. An indeed the
Windows 7 box on which I observe the problems has some of them
installed (e.g. McAffe {Agent, GTI Proxy Agent, Intrusion Prevention,
VirusScan Enterprise, AntySpywaare Enterprise} to name just a few).
On the other hand, on the same Windows 7 box I have a virtual machine
running inside VirtualBox with WindowsXP which has the same McAffe
software installed and it is running without any problems. The OpenJDK
build always succeeds in the virtual machine!
So I'm not quite sure of this is:
- a problem of some additional software which is running on my Windows
7 box and interferes with Cygwin
- a general Windows7 problem
- a problem of the specific Cygwin version I'm using
- a problem of Cygwin running on 64-bit Windows 7
I'll try to further narrow down the problem, but of course any hints
are highly welcome (unfortunately I can't easily get rid of the McAffe
stuff without losing my job, so please don't advise this:)
Regards,
Volker
PS: below you can find the exact versions of the software/hardware I'm using:
64-bit Windows 7, SP 1
Dual Core Intel i7, 8GB RAM
Cygwin (output of uname -a):
CYGWIN_NT-6.1-WOW64 WDFN00299915A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
In the Virtual box VM I have the following system:
64-bit Windows XP Professional Version 2003 SP 2
Cygwin (output of uname -a):
CYGWIN_NT-5.2-WOW64 WDFV00248216A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
On Tue, Jan 24, 2012 at 5:52 PM, Pete Brunetpeter.bru...@oracle.com wrote:
Is anyone able to build on Win 7? I'm on my 8th build hoping to get to
the end and have seen these errors:
out of memory, 3 times - I have more than enough memory
fork: Resource temporarily unavailable, 3 times
error 126, once
I have read http://cygwin.com/faq-nochunks.html#faq.using.bloda so
apparently something on my system is causing a problem but I haven't
been successful in finding it yet. I have my Norton 360 Auto-Protect
turned off. It would be helpful to know if anyone has successfully
built on Win 7 and also if anyone has ideas on what I might look for
beyond what is listed in the cygwin FAQ.
Thanks, Pete
Re: Is anyone able to build on Win 7
, VirusScan Enterprise, AntySpywaare Enterprise} to name just a few). On the other hand, on the same Windows 7 box I have a virtual machine running inside VirtualBox with WindowsXP which has the same McAffe software installed and it is running without any problems. The OpenJDK build always succeeds in the virtual machine! So I'm not quite sure of this is: - a problem of some additional software which is running on my Windows 7 box and interferes with Cygwin - a general Windows7 problem - a problem of the specific Cygwin version I'm using - a problem of Cygwin running on 64-bit Windows 7 I'll try to further narrow down the problem, but of course any hints are highly welcome (unfortunately I can't easily get rid of the McAffe stuff without losing my job, so please don't advise this:) Regards, Volker PS: below you can find the exact versions of the software/hardware I'm using: 64-bit Windows 7, SP 1 Dual Core Intel i7, 8GB RAM Cygwin (output of uname -a): CYGWIN_NT-6.1-WOW64 WDFN00299915A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin bash 4.1.10(4) // installed by Cygwin setup.exe make 3.82 // compiled by myself In the Virtual box VM I have the following system: 64-bit Windows XP Professional Version 2003 SP 2 Cygwin (output of uname -a): CYGWIN_NT-5.2-WOW64 WDFV00248216A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin bash 4.1.10(4) // installed by Cygwin setup.exe make 3.82 // compiled by myself On Tue, Jan 24, 2012 at 5:52 PM, Pete Brunet peter.bru...@oracle.com wrote: Is anyone able to build on Win 7? I'm on my 8th build hoping to get to the end and have seen these errors: out of memory, 3 times - I have more than enough memory fork: Resource temporarily unavailable, 3 times error 126, once I have read http://cygwin.com/faq-nochunks.html#faq.using.bloda so apparently something on my system is causing a problem but I haven't been successful in finding it yet. I have my Norton 360 Auto-Protect turned off. It would be helpful to know if anyone has successfully built on Win 7 and also if anyone has ideas on what I might look for beyond what is listed in the cygwin FAQ. Thanks, Pete
Re: Is anyone able to build on Win 7
(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
GNU bash, version 4.1.10(4)-release (i686-pc-cygwin)
GNU Make 3.81
Pete
On 1/25/12 9:06 AM, Volker Simonis wrote:
Hi Peter,
glad to see that other have the same problems:)
But seriously, on Windows 7 I'm currently experiencing the same
massive build problems and I'm not sure what the root cause of these
problems is.
I found the following bug which exactly describes the problems I'm
facing:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6903517
Among others, these are:
- rm: cannot remove directory `META-INF': Directory not empty
- error: cannot create example2.html: Permission denied
- [javac]
C:\Software\OpenJDK\jdk8\langtools\src\share\classes\com\sun\tools\javac\util\SharedNameTable.java:40:
error: error while writing SharedNameTable:
c:\Software\OpenJDK\output_amd64\langtools\build\bootstrap\classes\com\sun\tools\javac\util\SharedNameTable.class
(Access is denied)
but I also saw the 'out of memory' and 'for' problems mentioned by you.
The description of bug 6903517 references the Big List of Dodgy Apps
(http://cygwin.com/faq/faq.using.html#faq.using.bloda). This is a list
in the Cygwin FAQ which lists applications like Virus Scanners which
can interfere with Cygwin in an unpredictable way. An indeed the
Windows 7 box on which I observe the problems has some of them
installed (e.g. McAffe {Agent, GTI Proxy Agent, Intrusion Prevention,
VirusScan Enterprise, AntySpywaare Enterprise} to name just a few).
On the other hand, on the same Windows 7 box I have a virtual machine
running inside VirtualBox with WindowsXP which has the same McAffe
software installed and it is running without any problems. The OpenJDK
build always succeeds in the virtual machine!
So I'm not quite sure of this is:
- a problem of some additional software which is running on my Windows
7 box and interferes with Cygwin
- a general Windows7 problem
- a problem of the specific Cygwin version I'm using
- a problem of Cygwin running on 64-bit Windows 7
I'll try to further narrow down the problem, but of course any hints
are highly welcome (unfortunately I can't easily get rid of the McAffe
stuff without losing my job, so please don't advise this:)
Regards,
Volker
PS: below you can find the exact versions of the software/hardware I'm
using:
64-bit Windows 7, SP 1
Dual Core Intel i7, 8GB RAM
Cygwin (output of uname -a):
CYGWIN_NT-6.1-WOW64 WDFN00299915A 1.7.9(0.237/5/3) 2011-03-29 10:10
i686 Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
In the Virtual box VM I have the following system:
64-bit Windows XP Professional Version 2003 SP 2
Cygwin (output of uname -a):
CYGWIN_NT-5.2-WOW64 WDFV00248216A 1.7.9(0.237/5/3) 2011-03-29 10:10
i686 Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
On Tue, Jan 24, 2012 at 5:52 PM, Pete Brunetpeter.bru...@oracle.com
wrote:
Is anyone able to build on Win 7? I'm on my 8th build hoping to get to
the end and have seen these errors:
out of memory, 3 times - I have more than enough memory
fork: Resource temporarily unavailable, 3 times
error 126, once
I have read http://cygwin.com/faq-nochunks.html#faq.using.bloda so
apparently something on my system is causing a problem but I haven't
been successful in finding it yet. I have my Norton 360 Auto-Protect
turned off. It would be helpful to know if anyone has successfully
built on Win 7 and also if anyone has ideas on what I might look for
beyond what is listed in the cygwin FAQ.
Thanks, Pete
Re: Is anyone able to build on Win 7
On Feb 1, 2012, at 9:43 AM, Volker Simonis wrote: Quite contrary to Cygwin 1.7.9, the build reproducibly freezes after finishing jdk/make/java/jvm when entering jdk/make/java/redist and I hove no idea why. So the bad news is that the build problems on Windows7 will eventually get even worse with the next version of Cygwin. for the most part jdk/make/java/redist is copying files. That smells like an anti-virus on-access scanning issue. You might try turning off AV on-access scanning temporarily and see if that changes things. Or add your source tree and build result area to the AV directory exclude list temporarily. Of course, changing AV settings is a dangerous notice I said 'temporarily'. Ultimate AV solution is Linux or Solaris of course. ;^) Has anyone invented a Windows application build system that runs on Linux? ;^) -kto
Re: Is anyone able to build on Win 7
Hi Peter,
glad to see that other have the same problems:)
But seriously, on Windows 7 I'm currently experiencing the same
massive build problems and I'm not sure what the root cause of these
problems is.
I found the following bug which exactly describes the problems I'm facing:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6903517
Among others, these are:
- rm: cannot remove directory `META-INF': Directory not empty
- error: cannot create example2.html: Permission denied
- [javac]
C:\Software\OpenJDK\jdk8\langtools\src\share\classes\com\sun\tools\javac\util\SharedNameTable.java:40:
error: error while writing SharedNameTable:
c:\Software\OpenJDK\output_amd64\langtools\build\bootstrap\classes\com\sun\tools\javac\util\SharedNameTable.class
(Access is denied)
but I also saw the 'out of memory' and 'for' problems mentioned by you.
The description of bug 6903517 references the Big List of Dodgy Apps
(http://cygwin.com/faq/faq.using.html#faq.using.bloda). This is a list
in the Cygwin FAQ which lists applications like Virus Scanners which
can interfere with Cygwin in an unpredictable way. An indeed the
Windows 7 box on which I observe the problems has some of them
installed (e.g. McAffe {Agent, GTI Proxy Agent, Intrusion Prevention,
VirusScan Enterprise, AntySpywaare Enterprise} to name just a few).
On the other hand, on the same Windows 7 box I have a virtual machine
running inside VirtualBox with WindowsXP which has the same McAffe
software installed and it is running without any problems. The OpenJDK
build always succeeds in the virtual machine!
So I'm not quite sure of this is:
- a problem of some additional software which is running on my Windows
7 box and interferes with Cygwin
- a general Windows7 problem
- a problem of the specific Cygwin version I'm using
- a problem of Cygwin running on 64-bit Windows 7
I'll try to further narrow down the problem, but of course any hints
are highly welcome (unfortunately I can't easily get rid of the McAffe
stuff without losing my job, so please don't advise this:)
Regards,
Volker
PS: below you can find the exact versions of the software/hardware I'm using:
64-bit Windows 7, SP 1
Dual Core Intel i7, 8GB RAM
Cygwin (output of uname -a):
CYGWIN_NT-6.1-WOW64 WDFN00299915A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
In the Virtual box VM I have the following system:
64-bit Windows XP Professional Version 2003 SP 2
Cygwin (output of uname -a):
CYGWIN_NT-5.2-WOW64 WDFV00248216A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
On Tue, Jan 24, 2012 at 5:52 PM, Pete Brunet peter.bru...@oracle.com wrote:
Is anyone able to build on Win 7? I'm on my 8th build hoping to get to
the end and have seen these errors:
out of memory, 3 times - I have more than enough memory
fork: Resource temporarily unavailable, 3 times
error 126, once
I have read http://cygwin.com/faq-nochunks.html#faq.using.bloda so
apparently something on my system is causing a problem but I haven't
been successful in finding it yet. I have my Norton 360 Auto-Protect
turned off. It would be helpful to know if anyone has successfully
built on Win 7 and also if anyone has ideas on what I might look for
beyond what is listed in the cygwin FAQ.
Thanks, Pete
Re: Is anyone able to build on Win 7
Thanks Volker, I was thinking I'm going to have to try using XP in a
VM. My W7 config is very close to yours (make 3.81 instead of 3.82).
W7 Pro, 64 bit, SP1
Intel Core 2 Duo, P8700, 2.53 GHz, 8 GB RAM
CYGWIN_NT-6.1-WOW64 Bevo 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
GNU bash, version 4.1.10(4)-release (i686-pc-cygwin)
GNU Make 3.81
Pete
On 1/25/12 9:06 AM, Volker Simonis wrote:
Hi Peter,
glad to see that other have the same problems:)
But seriously, on Windows 7 I'm currently experiencing the same
massive build problems and I'm not sure what the root cause of these
problems is.
I found the following bug which exactly describes the problems I'm facing:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6903517
Among others, these are:
- rm: cannot remove directory `META-INF': Directory not empty
- error: cannot create example2.html: Permission denied
- [javac]
C:\Software\OpenJDK\jdk8\langtools\src\share\classes\com\sun\tools\javac\util\SharedNameTable.java:40:
error: error while writing SharedNameTable:
c:\Software\OpenJDK\output_amd64\langtools\build\bootstrap\classes\com\sun\tools\javac\util\SharedNameTable.class
(Access is denied)
but I also saw the 'out of memory' and 'for' problems mentioned by you.
The description of bug 6903517 references the Big List of Dodgy Apps
(http://cygwin.com/faq/faq.using.html#faq.using.bloda). This is a list
in the Cygwin FAQ which lists applications like Virus Scanners which
can interfere with Cygwin in an unpredictable way. An indeed the
Windows 7 box on which I observe the problems has some of them
installed (e.g. McAffe {Agent, GTI Proxy Agent, Intrusion Prevention,
VirusScan Enterprise, AntySpywaare Enterprise} to name just a few).
On the other hand, on the same Windows 7 box I have a virtual machine
running inside VirtualBox with WindowsXP which has the same McAffe
software installed and it is running without any problems. The OpenJDK
build always succeeds in the virtual machine!
So I'm not quite sure of this is:
- a problem of some additional software which is running on my Windows
7 box and interferes with Cygwin
- a general Windows7 problem
- a problem of the specific Cygwin version I'm using
- a problem of Cygwin running on 64-bit Windows 7
I'll try to further narrow down the problem, but of course any hints
are highly welcome (unfortunately I can't easily get rid of the McAffe
stuff without losing my job, so please don't advise this:)
Regards,
Volker
PS: below you can find the exact versions of the software/hardware I'm using:
64-bit Windows 7, SP 1
Dual Core Intel i7, 8GB RAM
Cygwin (output of uname -a):
CYGWIN_NT-6.1-WOW64 WDFN00299915A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686
Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
In the Virtual box VM I have the following system:
64-bit Windows XP Professional Version 2003 SP 2
Cygwin (output of uname -a):
CYGWIN_NT-5.2-WOW64 WDFV00248216A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686
Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
On Tue, Jan 24, 2012 at 5:52 PM, Pete Brunet peter.bru...@oracle.com wrote:
Is anyone able to build on Win 7? I'm on my 8th build hoping to get to
the end and have seen these errors:
out of memory, 3 times - I have more than enough memory
fork: Resource temporarily unavailable, 3 times
error 126, once
I have read http://cygwin.com/faq-nochunks.html#faq.using.bloda so
apparently something on my system is causing a problem but I haven't
been successful in finding it yet. I have my Norton 360 Auto-Protect
turned off. It would be helpful to know if anyone has successfully
built on Win 7 and also if anyone has ideas on what I might look for
beyond what is listed in the cygwin FAQ.
Thanks, Pete
Re: Is anyone able to build on Win 7
I started W7 in safe mode and the build failed with a fork failure. I
think that eliminates things in the BLODA list. If anyone out there is
building OK on W7 please send your configuration, e.g. as shown below.
Maybe that will suggest a different version of cygwin or bash. -Pete
On 1/25/12 9:55 AM, Pete Brunet wrote:
Thanks Volker, I was thinking I'm going to have to try using XP in a
VM. My W7 config is very close to yours (make 3.81 instead of 3.82).
W7 Pro, 64 bit, SP1
Intel Core 2 Duo, P8700, 2.53 GHz, 8 GB RAM
CYGWIN_NT-6.1-WOW64 Bevo 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
GNU bash, version 4.1.10(4)-release (i686-pc-cygwin)
GNU Make 3.81
Pete
On 1/25/12 9:06 AM, Volker Simonis wrote:
Hi Peter,
glad to see that other have the same problems:)
But seriously, on Windows 7 I'm currently experiencing the same
massive build problems and I'm not sure what the root cause of these
problems is.
I found the following bug which exactly describes the problems I'm facing:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6903517
Among others, these are:
- rm: cannot remove directory `META-INF': Directory not empty
- error: cannot create example2.html: Permission denied
- [javac]
C:\Software\OpenJDK\jdk8\langtools\src\share\classes\com\sun\tools\javac\util\SharedNameTable.java:40:
error: error while writing SharedNameTable:
c:\Software\OpenJDK\output_amd64\langtools\build\bootstrap\classes\com\sun\tools\javac\util\SharedNameTable.class
(Access is denied)
but I also saw the 'out of memory' and 'for' problems mentioned by you.
The description of bug 6903517 references the Big List of Dodgy Apps
(http://cygwin.com/faq/faq.using.html#faq.using.bloda). This is a list
in the Cygwin FAQ which lists applications like Virus Scanners which
can interfere with Cygwin in an unpredictable way. An indeed the
Windows 7 box on which I observe the problems has some of them
installed (e.g. McAffe {Agent, GTI Proxy Agent, Intrusion Prevention,
VirusScan Enterprise, AntySpywaare Enterprise} to name just a few).
On the other hand, on the same Windows 7 box I have a virtual machine
running inside VirtualBox with WindowsXP which has the same McAffe
software installed and it is running without any problems. The OpenJDK
build always succeeds in the virtual machine!
So I'm not quite sure of this is:
- a problem of some additional software which is running on my Windows
7 box and interferes with Cygwin
- a general Windows7 problem
- a problem of the specific Cygwin version I'm using
- a problem of Cygwin running on 64-bit Windows 7
I'll try to further narrow down the problem, but of course any hints
are highly welcome (unfortunately I can't easily get rid of the McAffe
stuff without losing my job, so please don't advise this:)
Regards,
Volker
PS: below you can find the exact versions of the software/hardware I'm using:
64-bit Windows 7, SP 1
Dual Core Intel i7, 8GB RAM
Cygwin (output of uname -a):
CYGWIN_NT-6.1-WOW64 WDFN00299915A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686
Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
In the Virtual box VM I have the following system:
64-bit Windows XP Professional Version 2003 SP 2
Cygwin (output of uname -a):
CYGWIN_NT-5.2-WOW64 WDFV00248216A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686
Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
On Tue, Jan 24, 2012 at 5:52 PM, Pete Brunet peter.bru...@oracle.com wrote:
Is anyone able to build on Win 7? I'm on my 8th build hoping to get to
the end and have seen these errors:
out of memory, 3 times - I have more than enough memory
fork: Resource temporarily unavailable, 3 times
error 126, once
I have read http://cygwin.com/faq-nochunks.html#faq.using.bloda so
apparently something on my system is causing a problem but I haven't
been successful in finding it yet. I have my Norton 360 Auto-Protect
turned off. It would be helpful to know if anyone has successfully
built on Win 7 and also if anyone has ideas on what I might look for
beyond what is listed in the cygwin FAQ.
Thanks, Pete
Re: Is anyone able to build on Win 7
Sorry guys, I don't have the time or priority to track this down.
Official builds are still happening on Windows XP and Windows 2003 X64 and these
problems are not being seen on those systems yet...
although we recently have been visited by the McAfee plague so maybe it's just
a matter of time. ;^(
Someone with some strong Windows experience needs to run this to ground.
We do need this to work, eventually.
-kto
On Jan 25, 2012, at 9:09 AM, Pete Brunet wrote:
I started W7 in safe mode and the build failed with a fork failure. I
think that eliminates things in the BLODA list. If anyone out there is
building OK on W7 please send your configuration, e.g. as shown below.
Maybe that will suggest a different version of cygwin or bash. -Pete
On 1/25/12 9:55 AM, Pete Brunet wrote:
Thanks Volker, I was thinking I'm going to have to try using XP in a
VM. My W7 config is very close to yours (make 3.81 instead of 3.82).
W7 Pro, 64 bit, SP1
Intel Core 2 Duo, P8700, 2.53 GHz, 8 GB RAM
CYGWIN_NT-6.1-WOW64 Bevo 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
GNU bash, version 4.1.10(4)-release (i686-pc-cygwin)
GNU Make 3.81
Pete
On 1/25/12 9:06 AM, Volker Simonis wrote:
Hi Peter,
glad to see that other have the same problems:)
But seriously, on Windows 7 I'm currently experiencing the same
massive build problems and I'm not sure what the root cause of these
problems is.
I found the following bug which exactly describes the problems I'm facing:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6903517
Among others, these are:
- rm: cannot remove directory `META-INF': Directory not empty
- error: cannot create example2.html: Permission denied
- [javac]
C:\Software\OpenJDK\jdk8\langtools\src\share\classes\com\sun\tools\javac\util\SharedNameTable.java:40:
error: error while writing SharedNameTable:
c:\Software\OpenJDK\output_amd64\langtools\build\bootstrap\classes\com\sun\tools\javac\util\SharedNameTable.class
(Access is denied)
but I also saw the 'out of memory' and 'for' problems mentioned by you.
The description of bug 6903517 references the Big List of Dodgy Apps
(http://cygwin.com/faq/faq.using.html#faq.using.bloda). This is a list
in the Cygwin FAQ which lists applications like Virus Scanners which
can interfere with Cygwin in an unpredictable way. An indeed the
Windows 7 box on which I observe the problems has some of them
installed (e.g. McAffe {Agent, GTI Proxy Agent, Intrusion Prevention,
VirusScan Enterprise, AntySpywaare Enterprise} to name just a few).
On the other hand, on the same Windows 7 box I have a virtual machine
running inside VirtualBox with WindowsXP which has the same McAffe
software installed and it is running without any problems. The OpenJDK
build always succeeds in the virtual machine!
So I'm not quite sure of this is:
- a problem of some additional software which is running on my Windows
7 box and interferes with Cygwin
- a general Windows7 problem
- a problem of the specific Cygwin version I'm using
- a problem of Cygwin running on 64-bit Windows 7
I'll try to further narrow down the problem, but of course any hints
are highly welcome (unfortunately I can't easily get rid of the McAffe
stuff without losing my job, so please don't advise this:)
Regards,
Volker
PS: below you can find the exact versions of the software/hardware I'm
using:
64-bit Windows 7, SP 1
Dual Core Intel i7, 8GB RAM
Cygwin (output of uname -a):
CYGWIN_NT-6.1-WOW64 WDFN00299915A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686
Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
In the Virtual box VM I have the following system:
64-bit Windows XP Professional Version 2003 SP 2
Cygwin (output of uname -a):
CYGWIN_NT-5.2-WOW64 WDFV00248216A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686
Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
On Tue, Jan 24, 2012 at 5:52 PM, Pete Brunet peter.bru...@oracle.com
wrote:
Is anyone able to build on Win 7? I'm on my 8th build hoping to get to
the end and have seen these errors:
out of memory, 3 times - I have more than enough memory
fork: Resource temporarily unavailable, 3 times
error 126, once
I have read http://cygwin.com/faq-nochunks.html#faq.using.bloda so
apparently something on my system is causing a problem but I haven't
been successful in finding it yet. I have my Norton 360 Auto-Protect
turned off. It would be helpful to know if anyone has successfully
built on Win 7 and also if anyone has ideas on what I might look for
beyond what is listed in the cygwin FAQ.
Thanks, Pete
Re: Is anyone able to build on Win 7
I just had success with the following changes:
- downgraded from cygwin 1.7.9 (with bash 4.1.10) to 1.7.0 (with bash
3.2.49)
- changed ...\jdk\make\docs\Makefile line 74
ifeq ($(ARCH_DATA_MODEL),64)
MAX_VM_MEMORY = 1024
else
MAX_VM_MEMORY = 1024 --- This was 512
endif
I've only done one build and in prior builds had other issues besides
the memory problem, i.e. fork and error 126, but there's always hope.
If others could report their W7 configurations and whether or not there
were problems, that would be helpful.
Pete
On 1/25/12 6:17 PM, Kelly O'Hair wrote:
Sorry guys, I don't have the time or priority to track this down.
Official builds are still happening on Windows XP and Windows 2003 X64 and
these
problems are not being seen on those systems yet...
although we recently have been visited by the McAfee plague so maybe it's
just a matter of time. ;^(
Someone with some strong Windows experience needs to run this to ground.
We do need this to work, eventually.
-kto
On Jan 25, 2012, at 9:09 AM, Pete Brunet wrote:
I started W7 in safe mode and the build failed with a fork failure. I
think that eliminates things in the BLODA list. If anyone out there is
building OK on W7 please send your configuration, e.g. as shown below.
Maybe that will suggest a different version of cygwin or bash. -Pete
On 1/25/12 9:55 AM, Pete Brunet wrote:
Thanks Volker, I was thinking I'm going to have to try using XP in a
VM. My W7 config is very close to yours (make 3.81 instead of 3.82).
W7 Pro, 64 bit, SP1
Intel Core 2 Duo, P8700, 2.53 GHz, 8 GB RAM
CYGWIN_NT-6.1-WOW64 Bevo 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
GNU bash, version 4.1.10(4)-release (i686-pc-cygwin)
GNU Make 3.81
Pete
On 1/25/12 9:06 AM, Volker Simonis wrote:
Hi Peter,
glad to see that other have the same problems:)
But seriously, on Windows 7 I'm currently experiencing the same
massive build problems and I'm not sure what the root cause of these
problems is.
I found the following bug which exactly describes the problems I'm facing:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6903517
Among others, these are:
- rm: cannot remove directory `META-INF': Directory not empty
- error: cannot create example2.html: Permission denied
- [javac]
C:\Software\OpenJDK\jdk8\langtools\src\share\classes\com\sun\tools\javac\util\SharedNameTable.java:40:
error: error while writing SharedNameTable:
c:\Software\OpenJDK\output_amd64\langtools\build\bootstrap\classes\com\sun\tools\javac\util\SharedNameTable.class
(Access is denied)
but I also saw the 'out of memory' and 'for' problems mentioned by you.
The description of bug 6903517 references the Big List of Dodgy Apps
(http://cygwin.com/faq/faq.using.html#faq.using.bloda). This is a list
in the Cygwin FAQ which lists applications like Virus Scanners which
can interfere with Cygwin in an unpredictable way. An indeed the
Windows 7 box on which I observe the problems has some of them
installed (e.g. McAffe {Agent, GTI Proxy Agent, Intrusion Prevention,
VirusScan Enterprise, AntySpywaare Enterprise} to name just a few).
On the other hand, on the same Windows 7 box I have a virtual machine
running inside VirtualBox with WindowsXP which has the same McAffe
software installed and it is running without any problems. The OpenJDK
build always succeeds in the virtual machine!
So I'm not quite sure of this is:
- a problem of some additional software which is running on my Windows
7 box and interferes with Cygwin
- a general Windows7 problem
- a problem of the specific Cygwin version I'm using
- a problem of Cygwin running on 64-bit Windows 7
I'll try to further narrow down the problem, but of course any hints
are highly welcome (unfortunately I can't easily get rid of the McAffe
stuff without losing my job, so please don't advise this:)
Regards,
Volker
PS: below you can find the exact versions of the software/hardware I'm
using:
64-bit Windows 7, SP 1
Dual Core Intel i7, 8GB RAM
Cygwin (output of uname -a):
CYGWIN_NT-6.1-WOW64 WDFN00299915A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686
Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
In the Virtual box VM I have the following system:
64-bit Windows XP Professional Version 2003 SP 2
Cygwin (output of uname -a):
CYGWIN_NT-5.2-WOW64 WDFV00248216A 1.7.9(0.237/5/3) 2011-03-29 10:10 i686
Cygwin
bash 4.1.10(4) // installed by Cygwin setup.exe
make 3.82 // compiled by myself
On Tue, Jan 24, 2012 at 5:52 PM, Pete Brunet peter.bru...@oracle.com
wrote:
Is anyone able to build on Win 7? I'm on my 8th build hoping to get to
the end and have seen these errors:
out of memory, 3 times - I have more than enough memory
fork: Resource temporarily unavailable, 3 times
error 126, once
I have read http://cygwin.com/faq-nochunks.html#faq.using.bloda so
apparently something on my system is causing a problem but I haven't
been
Is anyone able to build on Win 7
Is anyone able to build on Win 7? I'm on my 8th build hoping to get to the end and have seen these errors: out of memory, 3 times - I have more than enough memory fork: Resource temporarily unavailable, 3 times error 126, once I have read http://cygwin.com/faq-nochunks.html#faq.using.bloda so apparently something on my system is causing a problem but I haven't been successful in finding it yet. I have my Norton 360 Auto-Protect turned off. It would be helpful to know if anyone has successfully built on Win 7 and also if anyone has ideas on what I might look for beyond what is listed in the cygwin FAQ. Thanks, Pete
Re: Is anyone able to build on Win 7
Hello, I'm regularly building on my win 7 x64 laptop as part of the build-infra project (when needing to compare build results of the new and old build system). I recognize your problems but am not experiencing them at the moment. At this point I'm usually building jdk8. The fork problem is usually a sign of too long command lines. Moving your repo to a directory with a shorter path could help fixing that. Out of memory errors could be dependent on which boot jdk you are using. When building jdk8 I'm currently using jdk7 release. If that doesn't help it might be faulty logic in the makefiles that just set the wrong mx flags for your particular system. Hope that helps some! /Erik On 2012-01-24 17:52, Pete Brunet wrote: Is anyone able to build on Win 7? I'm on my 8th build hoping to get to the end and have seen these errors: out of memory, 3 times - I have more than enough memory fork: Resource temporarily unavailable, 3 times error 126, once I have read http://cygwin.com/faq-nochunks.html#faq.using.bloda so apparently something on my system is causing a problem but I haven't been successful in finding it yet. I have my Norton 360 Auto-Protect turned off. It would be helpful to know if anyone has successfully built on Win 7 and also if anyone has ideas on what I might look for beyond what is listed in the cygwin FAQ. Thanks, Pete
