Re: [mac] no MacOSX PPC version of DEV300 m33/m34 ?

[Maho NAKATA]

From: Eric Hoch <[EMAIL PROTECTED]>
Subject: Re: [mac] no MacOSX PPC version of DEV300 m33/m34 ?
Date: Mon, 10 Nov 2008 11:09:05 +0100

> Hi Maho, 
> Am Mon, 10 Nov 2008 13:47:27 +0900 (JST) schrieb Maho NAKATA:
> > Hello Thorsten,
> > (Cc: maeda-san)
> > 
> > From: Thorsten Bosbach <[EMAIL PROTECTED]>
> > Subject: [mac] no MacOSX PPC version of DEV300 m33/m34 ?
> > Date: Wed, 05 Nov 2008 11:43:54 +0100
> > 
> >> Hi,
> >> 
> >> I was waiting for a recent build of MacOSX PPC DEV300 m33 or newer.
> >> Is there any reason why there are only Intel builds available 
> >> and the last PPC build is on m32?
> >> 
> >>> ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/Dev_DEV300_m34
> >> 
> > 
> > 
> >> Is there any reason why there are only Intel builds available 
> >> and the last PPC build is on m32?
> > Yes.
> > 
> > There is a big issuse for MacOSX PPC builds. "regcomp" dumps core 
> > conditionally,
> > and not reproducible way, especially at instsetoo_native and many 
> > languages.  
> > 
> > Please refer
> > #i87969#: MacOSX : regcomp fails at instsetoo_native on PPC
> > #i77664#: build fails at i18npool/source/localedata/data conditionally
> > and help MacOSX porting team.
> > 
> > It is very annoying I'm suffering for many years.
> > This is the only one reason I cannot provide MacOSX PowerPC packages.
> > Note that these issues don't exist for Intel.
> > 
> > I talked with Stephan Bergmann at the OOoCon2008, and such kind of
> > "unexpected" errors, especially when one builds many languages.
> > (he told me about Solaris, helpcontent2 breaks some times with 
> > many languages,
> > and )
> 
> Just an idea. Can't you split building PPC versions in say two or 
> three groups. So that you first build the lacoles say from a to h 
> from i to q and from r to z. This might take longer to build but we 
> would have the PPC binaries. 

Hi Eric,

Thanks for your suggestion. It makes sense. Worth trying.
--with-lang="ALL" is problematic and nothing is the worst.

I adapted slightly different approach from you.
Following is a part of my build script. I build 1. with all locales,
2. move *res files to other place, 3. 16 locales at a time.
Maybe my workaround doesn't work. I'll employ your idea.

--------------------------------------
#workaround regcomp issue...
$buildlangs_at_a_time=16;
$already_built=0;
$max_try=5;
if (!(-e $package_stamp)) {
chdir("$WRKSRC");
system ("patch -p0 -R < ${PATCHDIR}/patch-splitpackage\n");
chdir("${WORKDIR}");

     open (POSTSET,"<$WRKSRC/solenv/inc/postset.mk") || die "Can't open file 
$WRKSRC/solenv/inc/postset.mk\n";
     while(<POSTSET>)
     {
         if(/completelangiso=/o ) {
             $langs=$_;
         }
     }
     $langs =~ s/=/ / ;
     $numoflangs = split(' ',$langs) - 1 - $already_built;
     for($i=1;$i<=$numoflangs;$i++){
         [EMAIL PROTECTED];
     }

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]