idlc looping compiling XContentEnumerationAccess.idl

[Bob Willcox]

While building editors/openoffice.org-2 the build runs along seemingly fine
till it gets to here:

-------------
rm -f ../../../../unxfbsdi.pro/misc/cssconnection.idls
cat /tmp/mkjw00zJ >>../../../../unxfbsdi.pro/misc/cssconnection.idls
/usr/ports/editors/openoffice.org-2/work/OOG680_m9/udkapi/com/sun/star/container
idlc @/tmp/mkzV32ev
idlc: compile 'XIdentifierAccess.idl' ... 
idlc: compile 'XIdentifierReplace.idl' ... 
idlc: compile 'XIdentifierContainer.idl' ... 
idlc: compile 'ContainerEvent.idl' ... 
idlc: compile 'ElementExistException.idl' ... 
idlc: compile 'NoSuchElementException.idl' ... 
idlc: compile 'XChild.idl' ... 
idlc: compile 'XUniqueIDAccess.idl' ... 
idlc: compile 'XComponentEnumeration.idl' ... 
idlc: compile 'XComponentEnumerationAccess.idl' ... 
idlc: compile 'XContainer.idl' ... 
idlc: compile 'XContainerApproveBroadcaster.idl' ... 
idlc: compile 'XContainerApproveListener.idl' ... 
idlc: compile 'XContainerListener.idl' ... 
idlc: compile 'XContainerQuery.idl' ... 
idlc: compile 'XContentEnumerationAccess.idl' ... 

At which point it hangs (loops on the idlc command, consuming all
available CPU cycles) forever. This is on a 6.3-release system with
updated ports tree (updated earlier today).

Any suggestions/ideas what may be wrong and what I can do to get
past this?

-- 
Bob Willcox                      A lack of planning on your part does
bob at immure.com                   not constitute an emergency on my part.
Austin, TX