Hi Senthilkumar,
Yes that was the reason and that fixed the problem. I did not get any warnings. Now should I run the winenv.bat file which is in $SRC_ROOT.
Have a look at <http://tools.openoffice.org/#Build>. You seem to try to build a 680/1.9.x/2.0 beta version, therfore I'd recommend you have a fresh look at: <http://tools.openoffice.org/dev_docs/build_windows_tcsh.html>
winenv.bat is for the build that uses the 4NT shell, and that is still broken ATM. Better use the cygwin tools.
Can you please confirm? Also I just have 5GB disk space free. Do I need more disk space(6GB) as told in http://tools.openoffice.org/dev_docs/build_windows_1.x.y.html
-----------------------------------------------------^^^^^ ?
But still, I really don't know how much space you need. I ususally build with --enable-crashdump as an extra configure option and the complete build of 1.9.m84 used 11.5 GB here and took 17h 65m on my W2K, AMD XP1700, 512MB system. (You can propably substract ~1 h because I build the mozilla binaries from scratch.)
Build Instructions (Building a Full Build of the Office Suite). My processor is faster and i also have more RAM then given in the specification. Also I only have a single machine(is there a chance that a crash during the build can damage the machine to a great extent). I am sorry if the question is wrong.
You can never rule out damage if a (Windows) system crashes. But a crash is usually induced by faulty drivers/viruses/(or the WIndows OS itself). User space programs should not be able to crash an OS. If they do, ask M$ for a refund and switch to a real operating system. ;)
And to answer your question: I build OOo since the pre 1.0.0 release and the build never crashed my system nor damaged it.
Volker
-- If you like my work consider: http://www.scytek.de/donations.html PGP/GPG key (ID: 0x9F8A785D) available from wwwkeys.de.pgp.net key-fingerprint 550D F17E B082 A3E9 F913 9E53 3D35 C9BA 9F8A 785D
signature.asc
Description: OpenPGP digital signature
