build of de-apache-openoffice-4.1.0 broken

[Dr. A. Haakh]

Am 08.08.2014 03:11, Don Lewis schrieb:
> On  7 Aug, To: bugReporter at Haakh.de wrote:
>> On  7 Aug, Dr. A. Haakh wrote:
>>> Hi,
>>>
>>> on this system
>>>
>>> FreeBSD Crabberio.Haakh.de 10.0-STABLE FreeBSD 10.0-STABLE #0 r269301:
>>> Wed Jul 30 18:36:57 CEST 2014    
>>> toor at Crabberio.Haakh.de:/usr/obj/usr/src/sys/CRABBERIO  amd64
>>>
>>> I get this error:
>>>
>>> =====================================================
>>> ERROR: ERROR: unopkg sync --verbose -env:UNO_JAVA_JFW_ENV_JREHOME=true
>>> 2>&1 | failed!
>>> in function: register_extensions
>>> **************************************************
>>> in function: register_extensionsstopping log at Thu Aug  7 09:41:29 2014
>>> dmake:  Error code 255, while making 'openoffice_en-US.archive'
>>>
>>> 1 module(s):
>>>     instsetoo_native
>>> need(s) to be rebuilt
>>>
>>> Reason(s):
>>>
>>> ERROR: error 65280 occurred while making
>>> /usr/ports/editors/openoffice-4/work/aoo-4.1.0/main/instsetoo_native/util
>>>
>>> When you have fixed the errors in that module you can resume the build
>>> by running:
>>>
>>>     build --from instsetoo_native
>>>
>>> *** Error code 1
>>>
>>> Stop.
>>> make: stopped in /usr/ports/editors/openoffice-4
>>> ** Command failed [exit code 1]: /usr/bin/script -qa
>>> /tmp/portupgrade20140807-77714-1z11122 env UPGRADE_TOOL=portupgrade
>>> UPGRADE_PORT=de-apache-openoffice-4.0.1_4 UPGRADE_PORT_VER=4.0.1_4 make
>>> BATCH=yes
>>> ** Fix the problem and try again.
>>> ** Listing the failed packages (-:ignored / *:skipped / !:failed)
>>>     ! editors/openoffice-4 (de-apache-openoffice-4.0.1_4)    (unknown
>>> build error)
>>> =====================================================
>>>
>>> Any ideas?
>> I just noticed the same failure on portsmon (also 10.0).  I've done most
>> of my builds on 8.4-STABLE and have never seen this problem.  I'm not
>> running 10.0 on anything here, but I did have success with 11.0-CURRENT
>> a while back.  I run that again to see if I can reproduce the problem.
>>
>> I did a web search and didn't find anything that looked relevant.
> I just broke for me on 11.0-CURRENT as well.  That's a regression
> because it was working before.
>
> I see that portsmon was able to build it on 9.x.
>
Any idea what might be the cause?