Hi *, (thanks Eric for moving it to porting list)
On 10/29/07, Eric Hoch <[EMAIL PROTECTED]> wrote: > Am Mon, 29 Oct 2007 11:52:34 +0900 (JST) schrieb Maho NAKATA: > > Hi, > > I have just uploaded MacOSX version of SRC680_m223 INTEL X11/AQUA m223? - you need to update your template :-)) > > at good-day. > > > > URI ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/SRC680_m234/ > > http://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/SRC680_m234/ > > > > Somehow my G5 builds are corrupted :( > > http://www.openoffice.org/issues/show_bug.cgi?id=82955 > > MacOSX PPC : Build fails at instsetoo_native; regcomp fails > > > > Christian Lohmaier, Eric Hoch have you ever encountered this issue? Yes, I encounter it from time to time. It seems to be dependent on the filesystem used. When using UFS as filesystem, I almost never got that error (but unfortunately regcomp did crash in other places like in binfilter and testtools to a way that it wasn't possible to build anymore - however I think that the filesystem just accumulated too much corruption over time). I now use HFS+ (journaled) again and now have the failures in instsetoo_native I can only guess, but IMHO it is due to the very bad filesystem performance and when doing parallel builds this error is easily hit. If you have a look at the tinderbox status pages, all the orange results for the Mac OSX tinderbox needed either a second (or third) "build" in instsetoo_native or needed multiple builds in i18npool (the localedata issue) > No this error for now didn't show up during my last PPC compile of > m233. But this may be because for now this is the only build I was > able to do. More to come. > > What makes me curious in your log is > > "dmake: Error code 255, while making 'openoffice_en-US.portable' > ---* tg_merge.mk *--- > > I cannot find this line in any of my build logs of m233 Intel or > OOG680_m5 Intel in instsetoo_native/unxma > cxp.pro/OpenOffice//logging/en-US/log_SRC680_en-US.log. It doesn't show up on a successful build, since it is a target name. (a makefile target) - but for the mac it doesn't matter anyway, since the packageformat switch isn't used at all - Mac OSX packaging uses the "staging" method (hardcoded) So even when you specify a format switch, it will still use the very same commands as when you don't specify it. It is unnecessary to specify, but doesn't hurt. > For me this looks like you are trying to build OOo portable for the > mac. I don't know if this is enabled by default since m234 since I > haven't tried to build m234 yet on PPC nor on Mac but if there is a > switch in configure which allows to disable the build of a portable > OOo you should try to explicit disable the build of the portable > OOo and see if this error still occures. No, that's a red herring as well. "portable" is not a portable OOo (like those you can run from a USB-stick), but specifies EPM's own package format (tarball with installscript) ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
