Re: Please fix: japanese doc compilation
> someone added a japanese translation of the docs, but after enabling > it (so it is distributed), I get error (see below). Can someone fix > this, or disable the translation? This is a blocking issue for > releasing 2.12.2. The Japanese translation is for texi2html only, I believe. I can't see an easy way to make it work with texinfo.tex, given that there is no equivalence to LaTeX's NFSS interface to select fonts. We would need a texi2latex translation so that we could use my CJK package (to be more precise, my CJKutf8.sty file). Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Please fix: japanese doc compilation
> We would need a texi2latex translation so that we could use my CJK > package (to be more precise, my CJKutf8.sty file). Alternatively, texinfo.tex needs to be hacked for (hard-coded) Japanese support. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: gub3 FP exception
Op zaterdag 17-01-2009 om 21:03 uur [tijdzone -0200], schreef Han-Wen Nienhuys: > trying a manual > > $ make DESTDIR=/tmp/foobar installp > why does DESTDIR not work on glibc-core? glibc (traditionally) uses install_root (an noone ever fixed this). Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.12.1 for cygwin?
Op maandag 12-01-2009 om 10:53 uur [tijdzone +0100], schreef Jan Nieuwenhuizen: > Google tells me it's probably easiest to ask you to use the new > -X/--no-verify command line option to setup.exe. Does this work, can I upload to Cygwin? Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: gub3 FP exception
OK thanks. For reasons I do not understand, issuing a PATH=/home/lilydev/vc/gub3/target/linux-x86/root/usr/cross/bin/:$PATH make install_root=/tmp/isr install triggers a compile of iconv, which ends in c_eh `i686-linux-gcc --print-file-name=crtend.o` /home/lilydev/vc/gub3/target/linux-x86/build/glibc-core-2.3/csu/crtn.o /home/lilydev/vc/gub3/target/linux-x86/root/usr/cross/bin/i686-linux-ld: cannot find -lgcc_eh collect2: ld returned 1 exit status make[2]: *** [/home/lilydev/vc/gub3/target/linux-x86/build/glibc-core-2.3/iconv/iconv_prog] Error 1 There is no libgcc_eh in the gub3 directory, find /home/lilydev/vc/gub3/target/linux-x86/root/ -name libgcc'*' => /home/lilydev/vc/gub3/target/linux-x86/root/usr/cross/lib/gcc/i686-linux/4.1.1/libgcc.a I do have libgcc_eh in gub2, and in /usr/lib/ [lily...@haring glibc-core-2.3]$ locate libgcc_eh/home/lilydev/vc/gub/target/darwin-ppc/root/usr/cross/lib/gcc/powerpc-apple-darwin7/4.1.1/libgcc_eh.a /home/lilydev/vc/gub/target/darwin-x86/root/usr/cross/lib/gcc/i686-apple-darwin8/4.2.3/libgcc_eh.a /home/lilydev/vc/gub/target/freebsd-64/root/usr/cross/lib/gcc/x86_64-freebsd6/4.1.2/libgcc_eh.a /home/lilydev/vc/gub/target/freebsd-x86/root/usr/cross/lib/gcc/i686-freebsd4/4.1.2/libgcc_eh.a /home/lilydev/vc/gub/target/linux-64/root/usr/lib/libgcc_eh.a /home/lilydev/vc/gub/target/linux-ppc/root/usr/lib/libgcc_eh.a /home/lilydev/vc/gub/target/linux-x86/root/usr/lib/libgcc_eh.a /home/lilytest/gub/target/linux-x86/system/usr/cross/lib/gcc/i686-linux/4.1.1/libgcc_eh.a /usr/lib/gcc/i386-redhat-linux/4.3.2/libgcc_eh.a On Mon, Jan 19, 2009 at 7:45 AM, Jan Nieuwenhuizen wrote: > Op zaterdag 17-01-2009 om 21:03 uur [tijdzone -0200], schreef Han-Wen > Nienhuys: > >> trying a manual >> >> $ make DESTDIR=/tmp/foobar installp > >> why does DESTDIR not work on glibc-core? > > glibc (traditionally) uses install_root (an noone ever fixed this). > > Jan. > > -- > Jan Nieuwenhuizen | GNU LilyPond - The music typesetter > http://www.xs4all.nl/~jantien | http://www.lilypond.org > > -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] Re: Remarks about the building process
I can't remember the status of this change, but LGTM -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Please fix: japanese doc compilation
Hello everyone, > ./lilypond-learning.pdftexi:58: Paragraph ended before > \documentlanguagetrywith > outunderscore was complete. > >\par > l.58 > > l.69: Unicode char \u8:音 not defined for Texinfo > l.69: Unicode char \u8:楽 not defined for Texinfo > l.69: Unicode char \u8:譜 not defined for Texinfo > l.69: Unicode char \u8:刻 not defined for Texinfo > I always get the messages like above while I am doing "make web". It will fail. But, I do "make web" twice or three times, then it will work well. Cheers, Sawada, Yoshiki ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: gub3 FP exception
Op maandag 19-01-2009 om 12:08 uur [tijdzone -0200], schreef Han-Wen Nienhuys: > OK thanks. For reasons I do not understand, issuing a Yes, well: UTSL! See gub/specs/glibc-core.py: def install_command (self): return (glibc.Glibc.install_command (self) .replace (' install ', ' install-lib-all install-headers ') # avoid -lgcc_eh, which gcc-core does not have + ' gnulib=-lgcc') HTH, Jan. > PATH=/home/lilydev/vc/gub3/target/linux-x86/root/usr/cross/bin/:$PATH > make install_root=/tmp/isr install > > triggers a compile of iconv, which ends in > > > c_eh `i686-linux-gcc --print-file-name=crtend.o` > /home/lilydev/vc/gub3/target/linux-x86/build/glibc-core-2.3/csu/crtn.o > /home/lilydev/vc/gub3/target/linux-x86/root/usr/cross/bin/i686-linux-ld: > cannot find -lgcc_eh > collect2: ld returned 1 exit status > make[2]: *** > [/home/lilydev/vc/gub3/target/linux-x86/build/glibc-core-2.3/iconv/iconv_prog] > Error 1 > > > There is no libgcc_eh in the gub3 directory, > > find /home/lilydev/vc/gub3/target/linux-x86/root/ -name libgcc'*' > => > > /home/lilydev/vc/gub3/target/linux-x86/root/usr/cross/lib/gcc/i686-linux/4.1.1/libgcc.a > > > I do have libgcc_eh in gub2, and in /usr/lib/ > > [lily...@haring glibc-core-2.3]$ locate > libgcc_eh/home/lilydev/vc/gub/target/darwin-ppc/root/usr/cross/lib/gcc/powerpc-apple-darwin7/4.1.1/libgcc_eh.a > /home/lilydev/vc/gub/target/darwin-x86/root/usr/cross/lib/gcc/i686-apple-darwin8/4.2.3/libgcc_eh.a > /home/lilydev/vc/gub/target/freebsd-64/root/usr/cross/lib/gcc/x86_64-freebsd6/4.1.2/libgcc_eh.a > /home/lilydev/vc/gub/target/freebsd-x86/root/usr/cross/lib/gcc/i686-freebsd4/4.1.2/libgcc_eh.a > /home/lilydev/vc/gub/target/linux-64/root/usr/lib/libgcc_eh.a > /home/lilydev/vc/gub/target/linux-ppc/root/usr/lib/libgcc_eh.a > /home/lilydev/vc/gub/target/linux-x86/root/usr/lib/libgcc_eh.a > /home/lilytest/gub/target/linux-x86/system/usr/cross/lib/gcc/i686-linux/4.1.1/libgcc_eh.a > /usr/lib/gcc/i386-redhat-linux/4.3.2/libgcc_eh.a > > > > On Mon, Jan 19, 2009 at 7:45 AM, Jan Nieuwenhuizen > wrote: > > Op zaterdag 17-01-2009 om 21:03 uur [tijdzone -0200], schreef Han-Wen > > Nienhuys: > > > >> trying a manual > >> > >> $ make DESTDIR=/tmp/foobar installp > > > >> why does DESTDIR not work on glibc-core? > > > > glibc (traditionally) uses install_root (an noone ever fixed this). > > > > Jan. > > > > -- > > Jan Nieuwenhuizen | GNU LilyPond - The music typesetter > > http://www.xs4all.nl/~jantien | http://www.lilypond.org > > > > > > > -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
(Follow up) Re: Please fix: japanese doc compilation
Hi, I will add a follow up. I guess the problem is caused by something participating with Japanese font. Therefore, if your computer does not have the font, it may be not able to fixed. Thanks, Sawada, Yoshiki ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel