xalanj on Snow Leopard and 1.8 - Very long build process

[Michael Franz]

All of the time is spent in the javadoc task of the build.  (which is what I
saw before the debug).  The ant task does not have enough memory, thus
slowing down the javadoc and causing some of the calls to fail.

  [javadoc]
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_java_xalanj/work/xalan-j_2_7_0/src/org/apache/xml/dtm/ref/dom2dtm/DOM2DTMdefaultNamespaceDeclarationNode.java:307:
warning - @param argument "namespaceURI" is not a parameter name.
  [javadoc] java.lang.OutOfMemoryError: Java heap space
  [javadoc]     at java.util.ArrayList.<init>(ArrayList.java:112)
  [javadoc]     at java.util.ArrayList.<init>(ArrayList.java:119)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.util.VisibleMemberMap$ClassMembers.addMembers(VisibleMemberMap.java:312)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.util.VisibleMemberMap$ClassMembers.mapClass(VisibleMemberMap.java:285)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.util.VisibleMemberMap$ClassMembers.mapClass(VisibleMemberMap.java:290)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.util.VisibleMemberMap$ClassMembers.mapClass(VisibleMemberMap.java:297)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.util.VisibleMemberMap$ClassMembers.build(VisibleMemberMap.java:280)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.util.VisibleMemberMap$ClassMembers.access$100(VisibleMemberMap.java:230)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.util.VisibleMemberMap.<init>(VisibleMemberMap.java:93)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.builders.MemberSummaryBuilder.init(MemberSummaryBuilder.java:88)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.builders.MemberSummaryBuilder.getInstance(MemberSummaryBuilder.java:64)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.builders.BuilderFactory.getMemberSummaryBuilder(BuilderFactory.java:191)
  [javadoc]     at
com.sun.tools.doclets.formats.html.ClassWriterImpl.navSummaryLinks(ClassWriterImpl.java:474)
  [javadoc]     at
com.sun.tools.doclets.formats.html.ClassWriterImpl.printSummaryDetailLinks(ClassWriterImpl.java:456)
  [javadoc]     at
com.sun.tools.doclets.formats.html.HtmlDocletWriter.navLinks(HtmlDocletWriter.java:462)
  [javadoc]     at
com.sun.tools.doclets.formats.html.ClassWriterImpl.writeHeader(ClassWriterImpl.java:125)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.buildClassHeader(ClassBuilder.java:164)
  [javadoc]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
  [javadoc]     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  [javadoc]     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  [javadoc]     at java.lang.reflect.Method.invoke(Method.java:597)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.invokeMethod(ClassBuilder.java:101)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.builders.AbstractBuilder.build(AbstractBuilder.java:90)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.buildClassDoc(ClassBuilder.java:124)
  [javadoc]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
  [javadoc]     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  [javadoc]     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  [javadoc]     at java.lang.reflect.Method.invoke(Method.java:597)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.invokeMethod(ClassBuilder.java:101)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.builders.AbstractBuilder.build(AbstractBuilder.java:90)
  [javadoc]     at
com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.build(ClassBuilder.java:108)
  [javadoc]     at
com.sun.tools.doclets.formats.html.HtmlDoclet.generateClassFiles(HtmlDoclet.java:155)

So, either the build script changed to not specify the memory or Snow
Leopard lowered the default memory setting on a Java process.



On Mon, Sep 7, 2009 at 9:15 AM, Michael Franz <mvfranz at gmail.com> wrote:

> Ryan,
>
> It finally finished after 90 minutes.  I will retry with the debug switch.
> I do not remember how log it took on leopard, but I am sure even 10 minutes
> is long.
>
> Thanks
>
>
> On Mon, Sep 7, 2009 at 8:13 AM, Ryan Schmidt <ryandesign at macports.org>wrote:
>
>>
>> On Sep 6, 2009, at 22:56, Michael Franz wrote:
>>
>>  I upgraded from Tiger to Snow Leopard.  I uninstalled all ports and
>>> removed macports 1.7 (followed the FAQ instructions).  Installed the Snow
>>> Leopard Xcode.  Installed macports 1.8 (Snow Leopard version).  I then tried
>>> to install xalanj.  xercesj installed fine, but the xalanj build has been
>>> running for almost an hour.
>>> 2544 ttys000    0:07.95 /usr/bin/tclsh /opt/local/bin/port install xalanj
>>>  2708 ttys000    0:00.00 sh -c  cd
>>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_java_xalanj/work/xalan-j_2_7_0"
>>> && ant all docs javadocs
>>>  2709 ttys000    0:20.73
>>> /System/Library/Frameworks/JavaVM.framework/Home/bin/java -classpath
>>> /usr/share/ant/lib/ant-launcher.jar -Dant.home=/usr/share/ant
>>> -Dant.library.dir=/usr/share/ant/lib -Djikes.class.p
>>>  2724 ttys000   52:30.53
>>> /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/bin/javadoc
>>> -breakiterator -d
>>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_
>>>
>>> Is there anyway to figure out what is happening?  I had no problem with
>>> this on Tiger and Leopard.
>>>
>>
>>
>> It built for me in under ten minutes on Snow Leopard (I didn't time it).
>>
>> You can look at Activity Monitor to see if any processes are using the CPU
>> heavily, which would indicate something is still going on.
>>
>> MacPorts will tell you what it's doing if you use the debug switch, but if
>> you did not start port with the debug switch, there isn't a way to make it
>> now start showing that information. You would have to cancel the port
>> install attempt and try again. You can add the debug switch now:
>>
>> sudo port -d install xalanj
>>
>> If it gets stuck at some point you should now be able to see it.
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090907/1d034467/attachment.html>