Hi Jim,

https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24

We only have to make sure, that we bundle the most recent msvcr100.dll
(32bit) for the windows build.
(see: .../main/external/msvcp100/README_msvcX100.dll.txt)

Regards, Matthias

P.S.: I will come back later with a full list of commits for the ASF
logos...


Am 02.05.2017 um 20:40 schrieb Jim Jagielski:
> Went OK... Will now kick off a x32 build...
>
> These are test builds, since we still have 2 backports pending::
>
>> On Mar 22, 2017, at 8:43 AM, Matthias Seidel <matthias.sei...@hamburg.de> 
>> wrote:
>>
>> Hi Raphael,
>>
>> Thank you for your effort!
>> Hopefully Ariel will still be able to assist, but it is really time for a 
>> 4.1.4 RC.
>>
>> May I suggest that these "release blocker" should also be merged:
>>
>> https://bz.apache.org/ooo/show_bug.cgi?id=127253
>> (Update the banners with the new ASF Logo)
> +1: It would be nice to have a complete list of changes required to
> backport from trunk though. Matthias if you want to go ahead and
> handle this, +1 from me.
>
>
>> https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24
>> (Java not recognized after update to AOO 4.1.3)
> REOPENED.
>
>
>> On May 2, 2017, at 9:27 AM, Jim Jagielski <j...@jagunet.com> wrote:
>>
>> FWIW, I've kicked off a CentOS5.11 x64 build on my VM.
>>
>> I've updated the wiki build page 
>> (https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step)
>> with some updates, most due to CentOS5 is now EOL and some urls
>> have changed. Plus, I needed to manually install File::Path
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to