Report an error when building on windows with new infrastructure

[Erik Joelsson]

The large printf lines are piped to files. I'm not aware of a way to 
write directly to a file from make. Are we using printf to print to the 
console anywhere? I know we use echo a lot in recipes.

/Erik

On 2012-05-21 20:03, Kelly O'Hair wrote:
> ERik,
>
> I'm wondering why printf is being used instead of the built in $(info) or $(warning) Make functions.
> Did you guys try those and run into issues?
> Seems like for spitting out debug or log information it would be faster, just curious.
>
> -kto
>
> On May 20, 2012, at 7:29 PM, Sean Chou wrote:
>
>> Hi Erik,
>>
>>      Thanks for your information. The build log is uploaded to
>> http://cr.openjdk.java.net/~zhouyx/buildinfra/build.log  . I misunderstood
>> the dot in 'Do this by running make VERBOSE=.'  in the guide and passed a
>> dot for verbose.
>>
>>      I'm using a build directory
>> "/cygdrive/e/openjdk/jdk8/jdk8-tl/build/mine" .
>>
>> On Fri, May 18, 2012 at 4:34 PM, Erik Joelsson<erik.joelsson at oracle.com>wrote:
>>
>>> Hello Sean,
>>>
>>> This is a known problem with Cygwin. Sometimes it happens intermittently
>>> (but that's mostly on windows 7 and 64bit) and sometimes it's very
>>> predictable. When it's predictable, like yours seems to be, it's usually
>>> caused by too long command lines. It would help us if you could post more
>>> of the buildlog, preferably with a "VERBOSE=" build so we can see where
>>> this happens and try to shorten command lines in that area.
>>>
>>> As a workaround, you could try shortening the path length to your source
>>> root directory. Say if you have your source in
>>> C:\some\deep\directory\with\a\**really\long\directory\path\**build-infra\,
>>> you could try moving it to c:\build-infra and see if that helps. A
>>> difference in the old and new build is that we use absolute paths for
>>> everything in the new build while the old used relative paths for most
>>> things, this makes us more sensitive to path depth for the source root.
>>>
>>> It looks like you added a dot to 'make VERBOSE= ', that would probably
>>> mess things up. The idea is to set the make variable VERBOSE to the empty
>>> string.
>>>
>>> /Erik
>>>
>>>
>>> On 2012-05-18 10:10, Sean Chou wrote:
>>>
>>>> Hi,
>>>>
>>>>      While trying to build on windows with new infrastructure, I got this
>>>> error:
>>>>
>>>> "/bin/sh: fork: retry: Resource temporarily unavailable
>>>> 2 [main] sh 2392 child_info_fork::abort: address space needed by
>>>> 'cygiconv
>>>> -2.dll' (0x674C0000) is already occupied"
>>>>
>>>>      And when   'make VERBOSE=. '  is used, it says "nothing to do for
>>>> all..."
>>>> and ' make VERBOSE="-d -p" '  builds something, but seems far from
>>>> complete.
>>>>
>>>>      The old build infrastructure works fine.
>>>>
>>>>      I'm building on windowsxp, both 32bit and 64bit.
>>>>
>>>> CYGWIN_NT-5.1 xxx 1.7.10(0.259/5/3) 2012-02-05 12:36 i686 Cygwin
>>>> CYGWIN_NT-5.2-xxx 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
>>>>
>>>>      Is this because XP is not supported ?
>>>>
>>>>
>>
>> -- 
>> Best Regards,
>> Sean Chou