Hello everyone,
I resolved the problem about ".po" file by myself.
Now, I know I should edit "ja.po" file in "Documentation/po"
and do "make po-update" ignoring error messages,
then do "make translation-status" in "Documentation".
Therefor, I just want to know whether my patch works well or not.
On Sat, Jan 3, 2009 at 12:52 PM, Jan Nieuwenhuizen
wrote:
>> make[2]: ***
>> [/home/lilydev/vc/gub3/target/linux-x86/build/glibc-core-2.3/sunrpc/xbootparam_prot.stmp]
>> Exceção
>> de ponto flutuante
>> make[2]: Saindo do diretório
>> `/home/lilydev/vc/gub3/target/linux-x86/src/glibc-core-2.3/s
I had a stray : in the LD_LIBRARY_PATH causing weirdness when
entering the build directory; however, even when removing that, I
still get the floating point error.
This is on Fedora 10.
On Sat, Jan 3, 2009 at 12:52 PM, Jan Nieuwenhuizen
wrote:
> Op donderdag 01-01-2009 om 17:54 uur [tijdzone -0
Op donderdag 01-01-2009 om 18:32 uur [tijdzone -0200], schreef Han-Wen
Nienhuys:
> I am seeing this too, and it is reproducible. Since it is an FP
> during the install stage, I would suspect some kind of low-level
> mismatch somewhere.
In an effort to push gub3 forward I just built up till gmp
On Sat, Jan 17, 2009 at 04:24:36PM +0800, Graham Breed wrote:
> David Kastrup wrote:
>> Graham Percival writes:
>>
>> It could be argued that some sort of Prolog-like system of specifying
>> limitations might be more natural. Or a TeX-like system of specifying
>> penalties for certain transiti
David Kastrup wrote:
Graham Percival writes:
That's not a terrible idea -- IIRC Sibelius and Finale already
have something like that built-in -- but it doesn't belong in the
main lilypond code. I'd recommend writing a separate tool, using
python or something like htat.
It could be ar
