Hello Mathias and Stephan.

Thanks for your comment.
My builds went fine. Now I'm uploading.
Best,

From: Mathias Bauer <[email protected]>
Subject: Re: [l10n-dev] DEV300_m40 fails @ dictionaries module, hu-HU
Date: Thu, 29 Jan 2009 11:22:27 +0100

> Maho NAKATA wrote:
> 
>> Hi Mathias!
>> 
>> Thanks for your comment.
>> 
>> From: Mathias Bauer <[email protected]>
>> Subject: Re: [l10n-dev] DEV300_m40 fails @ dictionaries module, hu-HU
>> Date: Wed, 28 Jan 2009 11:58:24 +0100
>> 
>>> The makefile.mk of the hungarian dictionary does not specify a custom
>>> license file and so by default the OOo license is chosen to be packed
>>> into the extension. The license file is not present in the solver at
>>> that time because a dependency in the build.lst of the dictionaries
>>> module is missing.
>> 
>> Aha there is a political issue, and workarounded...thanks.
>> 
>>> Please go to readlicense_oo and call "build" and "deliver" and try to
>>> build dictionaries again. That should work.
>> 
>> Yes, I did it and still fails. Then, as Stephan Bergmann told us
>> that there is a parallel build issue.
>> 
>>> A fix for this problem has been committed as issue 97267:
>>> 
>>> http://www.openoffice.org/issues/show_bug.cgi?id=97267
>> "WW8: export custom fields" so 97267 maybe a typo...
> 
> Oops sorry, it's in issue 98550, of course.
> 
>> I just started the clean build, and still I expect an build breakage.
> 
> The fix (declaring a custom license in makefile.mk of hu_HU) should help.
> 
> Ciao,
> Mathias
> 
> -- 
> Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
> OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
> Please don't reply to "[email protected]".
> I use it for the OOo lists and only rarely read other mails sent to it.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to