Hi Wei, *, On Fri, Jan 29, 2010 at 6:07 PM, Wei Zhang <[email protected]> wrote: > > (1) In the bug report http://www.openoffice.org/issues/show_bug.cgi?id=44627 > , it is said the version is 680m79, is this version the bug fixed version or > the buggy version ?
That is the version that the bug was found in - not necessarily the first one that did show the behaviour, but a "known to be bad" one. > Because I need to study the bug, so I need to build a > _buggy_ version, I am wondering how can I know which is the buggy version ? > ( will version 680m78 do ?) m79 should do. Earlier versions should do as well, and also later versions until the milestone that the fix was integrated in. > (2) After I have retrieved 680m79 from CVS, I found out that there is no > configure script in the SRC_ROOT/config_office directory, I am wondering > where should I find the configure script Hmm - there should be... but indeed - not in webinterface either - there is m78 (rev. 1.71), but the next one is m100 (rev 1.98) Seems like tags were lost. There are many revisions with the "integration cws: foo" comment, but no milestone-tag. To know when exactly it was fixed, you can use http://qa.openoffice.org/issuelinks.html to query EIS for the cws with the issue In this case, the cws was integrated into two codelines - SRC680_m157 and OOB680_m1 (the "Milestone (integrated)" column) > ------------------------------ quote > ------------------------------------------- > [Java framework] Using bootstrap parameter UNO_JAVA_JFW_ENV_CLASSPATH and > class path is: > /s/jdk1.4.2/jre/lib/rt.jar:.. > [Java framework] Using Java runtime library: > file:///afs/cs.wisc.edu/s/jdk1.4.2/i386_rh72/jre/lib/i386/client/libjvm.so. > osl_getsymbol: got Symbol JNI_CreateJavaVM > VM option: > -Djava.class.path=:/s/jdk1.4.2/jre/lib/rt.jar:.:/afs/cs.wisc.edu/s/jdk1.4.2/i386_rh72/jre/lib/plugin.jar > VM option: -Dorg.openoffice.native= > Segmentation fault Hmm - a segfault - no idea how to diagnose that, sorry :-( > I am wondering if there is any hint what should I do, it seems to me that > it has already built various components. As the error was in module "testtools", you can change to that directory and run "build" there, this will only try to build the module testtools I had problems with module testtools on the Mac, that were bypassed by just running build often enough, i.e. just trying again and again until it did succeed. Worth a try, but probably won't help. > And the configure parameters I used is following : > CC=gcc34 CXX=g++34 ./configure --prefix=/scratch/wei/usr/local/OOO_2.0.1/ prefix is ignored by OOo. > --enable-symbols --enable-debug --disable-mozilla I'd try without the --enable-symbols, and without --enable-debug for the initial builds - can still be enabled later, but the debug-build stuff is less tested. Java and ant version should be OK. ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
