Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jogischmidt@googlemail.com
 designates 209.85.214.47 as permitted sender)
Received-SPF: pass (google.com: domain of jogischmidt@googlemail.com
 designates 10.204.152.75 as permitted sender) client-ip=10.204.152.75;
Message-ID: <4F420CA9.6090107@googlemail.com>
Date: Mon, 20 Feb 2012 10:04:41 +0100
From: =?ISO-8859-1?Q?J=FCrgen_Schmidt?= <jogischmidt@googlemail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: Build breaks while making 'openoffice_en-US.archive'
References: <4F410528.7000201@t-online.de> <20120219163535.GA31899@localhost>
 <4F412958.60706@t-online.de> <20120219170416.GB31899@localhost>
 <4F417CDE.8030508@t-online.de> <4F41950C.1050903@apache.org>
In-Reply-To: <4F41950C.1050903@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 2/20/12 1:34 AM, Pedro Giffuni wrote:
> Hello;
>
> On 02/19/12 17:51, Regina Henschel wrote:
>>
>> I've copied those files to external\msvcp90 and made a clean build.
>> But it breaks again with error message
>> ERROR: ERROR: unopkg.exe sync --verbose
>> -env:UNO_JAVA_JFW_ENV_JREHOME=true 2>&1 | failed!
>> in function: register_extensions
>> and the already cited text in log_OOO340_en-US.log
>>
>> Searching with google I found that others, not connected to openoffice
>> and using MSVC directly, have similar problems when making a debug
>> build. The advise in those cases was to turn off "incremental
>> linking". But I have now knowledge of this.
>>
>> My non-pro build was successful in January with revision 1232793.
>>
>> Any further ideas?
>>
>
> I don't know if some changes I made late in January to reduce
> non-standard calls to GNU "cp -u" might have had any relationship
> but JIC I reverted the Windows part of it now in revision 1291096.

I would say we should stop guessing and should analyze the problem 
first. It doesn't make sense to revert changes from January when we had 
already successful build-bot builds on Windows in February.

Just my 2 cents

Juergen