Is anyone able to build on Win 7

[Kelly O'Hair]

Does this article provide any help:

https://kc.mcafee.com/corporate/index?page=content&id=KB55075&actp=search&viewlocale=en_US&searchid=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.brunet at 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
>>>>>> 
>>>>>>