Hi *, as promised here's another posting about my plays with o3-build.
Since the first install in a debian sarge didn't work at all, I created a chroot env with etch on that machine and tried again. The chroot is setup with a fairly minimal set of packages, and that's how you can detect the missing parts in o3-build :-) The build is currently still running, so there may be more problems, but this stuff is missing to get past configure stuff: * xmkmf (known issue, listed on the wiki-page already, but until it is added, the setgulls script could just specify --without-nas) * patch * zip/unzip (and bzip2) Configure doesn't complain, neither did the build break yet, but * file is missing as well, deliver makes use of it, and I guess it will cause problems later, at least when building the installset (hope I get that far :-)) I'm not sure to what extent the build-env should be self-contained, but since it contains stuff like editors and cvs, I think this should be added. Not needed to build OOo, but still very useful would be the following: * ccache * lndir (can help to both reduce disk-usage as well as ensuring clean, untouched sources to keep for cvs operations) That's it for this post, more to follow for sure.. ciao Christian -- NP: The Smashing Pumpkins - Porcelina Of The Vast Oceans --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
