On Thu, Mar 8, 2012 at 8:00 PM, Kelly O'Hair 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
>>
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
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 wil
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 :)
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
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
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 handlin
- 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
So
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
On Tue, Feb 14, 2012 at 12:43 PM, Fredrik Öhrström
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 res
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 AS
thout 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
>>>>&
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 '
;>>> - 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
>>>>&g
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 o
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 wor
ion 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
de 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:
>
(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 wrote:
Is anyone able to build on Win 7? I'm on my 8th buil
t; - 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
>>>&
t 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: belo
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 i6
gt; 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 Pr
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
>
> Cy
.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 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
t 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
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.blo
27 matches
Mail list logo
