Re: development on windows
Tim, have you used VMware before? This should allow you to compile LilyPond inside a virtual machine. I'm not certain what the best way is to transfer the iso from Jonathan to you, though. The goal of this iso to make it usable on a virtualization tool. The open source Sun VirtualBox can for example mount this as the virtual hard disk. Once it's ready maybe I can create a torrent? I've never done that before but it's probably the best way to transfer it. It'll take a while. I can also give you FTP access to one of the servers run by me where you could upload it. That would be the easiest. Bert ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: stable/2.12 and tagging of tarballs
In message 1244571546.25811.584.ca...@heerbeest, Jan Nieuwenhuizen janneke-l...@xs4all.nl writes I talked with Han-Wen about 2.10. The reason that we got up to 2.10.*33*, is that with git, doing stable bugfix releases is almost painless. Very little effort. We have small, contained patches/commits, that can be very easily cherry picked into stable. Now with CVS, it was hairy. This is a very nice and cheap way of supporting users. Users should not run development releases, but having fast-turnover regular stable bugfixing updates is *very* *very* nice. Like that 3/4 6/8 beaming issue ... (for those who didn't spot it, quavers in 3/4 time were grouped in threes!) Now I've got a big chunk of lilypond code with bugfixes for that, that will be redundant as soon as I upgrade. Imho it's a broken methodology that makes users put one version only bugfixes into their code. Fortunately, here, the user code is not going to be broken by a lily upgrade, but I expect that has (and will) happen. Cheers, Wol -- Anthony W. Youngman - anth...@thewolery.demon.co.uk ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc-build failure: pdfetex exit with bad status
On Wed, Jun 10, 2009 at 8:31 PM, Andrew Hawryluk ahawry...@gmail.comwrote: On Wed, Jun 10, 2009 at 5:45 AM, Jonathan Kulpjonlancek...@gmail.com wrote: On a fresh installation of Linux Mint (and previously of xubuntu, ubuntu, crunchbang, and ubuntulite) I can't get the docs to build properly. It's taking several make doc commands to get each of the pdf files to be written, and then when they appear they're missing all the images. Here's the tail of the terminal output: /b luesky/cm/cmtt12.pfb/usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmtt9.pfb /usr/share/texmf-texlive/fonts/type1/bluesky/latex-fonts/lcircle1.pfb Output written on lilypond.pdf (453 pages, 1615070 bytes). Transcript written on lilypond.log. /usr/bin/texi2dvi: pdfetex exited with bad status, quitting. make[1]: *** [out-www/lilypond.pdf] Error 1 make[1]: Leaving directory `/home/jon/lilypond/Documentation/user' make: *** [doc-stage-1] Error 2 When I was getting the same error a couple of moths ago I dug further into the .log file and found a line somewhere telling me which TeX package I was missing. (I think it was the 'epsf' package in my case.) Granted, you are already getting some output, so that may not be the case for you. Andrew Thanks, Andrew, I bet it is a missing TeX package. On my work partition I have a ton of texlive packages installed and I've never had a problem building the docs. I'm trying not to install anything extra on this experimental partition, trying to create a lilypond-dev-ready .iso of xubuntu (see development on Windows thread), and there must be something missing. I'm getting close though. Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: development on windows
On Thu, Jun 11, 2009 at 3:29 AM, Bertalan Fodor (LilyPondTool) lilypondt...@organum.hu wrote: Tim, have you used VMware before? This should allow you to compile LilyPond inside a virtual machine. I'm not certain what the best way is to transfer the iso from Jonathan to you, though. The goal of this iso to make it usable on a virtualization tool. The open source Sun VirtualBox can for example mount this as the virtual hard disk. Once it's ready maybe I can create a torrent? I've never done that before but it's probably the best way to transfer it. It'll take a while. I can also give you FTP access to one of the servers run by me where you could upload it. That would be the easiest. Bert Thanks, Bertalan, that would be great. I have a very slow upload speed, though, so it might be quicker to snail mail a DVD to someone. :) I'm close to having a solution to this. I created an .iso of my own regular xubuntu installation last night, installed it freshly this morning on a different partition, and the lilypond builds all worked perfectly. Just now I removed all of the software I think is superfluous and am running another doc-build. If it works I'll create an .iso from it and see how big it is. The one I made last night was huge, 1.5GB, but it had all the non-lily related stuff I always install and it wasn't created from a fresh OS install the way it's recommended. This one should be considerably smaller. Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
GUB missing Changelog and RELEASE-COMMIT
There were some FIXME remarks about darwin-ppc's libgcc, but I
think I can ignore them. A few mingw strip commands had command
barfed, such as libguile-srfi-srfi-60-v-2.l and
lilypond-windows.bat.in, but again I assume that I can ignore
those errors too.
This appears to be the thing that stops GUB, which is odd because
it worked on 2009-06-08, and the changes since then don't look as
though they would have changed this.
ln: accessing
`/home/lilypond/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-master/ChangeLog':
No such file or directory
ln: accessing
`/home/lilypond/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-master/RELEASE-COMMIT':
No such file or directory
make[5]: *** [local-dist] Error 1
make[5]: Leaving directory
`/home/lilypond/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-master'
make[4]: *** [dist] Error 2
make[4]: Leaving directory
`/home/lilypond/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-master'
cd
/home/lilypond/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-master/
make DOCUMENTATION=yes dist
Traceback (most recent call last):
File test-lily/dist-check.py, line 137, in module
main ()
File test-lily/dist-check.py, line 129, in main
system ('cd %(builddir)s/ make DOCUMENTATION=yes dist' %
locals ())
File test-lily/dist-check.py, line 56, in system
raise Exception ('failed')
Exception: failed
make[3]: *** [unlocked-dist-check] Error 1
-
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
[trivial patch] GUB avoid warning message
Trivial patch to avoid so much clutter in the log files. Cheers, - Graham From dfcef16797c0b4afe109a34421a8bc6f2fb846c9 Mon Sep 17 00:00:00 2001 From: Lilypond Documentation Project lilyp...@kainhofer.com Date: Thu, 11 Jun 2009 19:28:39 +0200 Subject: [PATCH] Remove unneeded warning message if uploads/signatures/ already exists. --- lilypond.make |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lilypond.make b/lilypond.make index 59331cf..0ce811f 100644 --- a/lilypond.make +++ b/lilypond.make @@ -188,7 +188,7 @@ unlocked-test-clean: rm -f $(call SIGNATURE_FUNCTION,cached-test-output) cached-dist-check cached-doc-export cached-test-export: - -mkdir uploads/signatures + -mkdir -p uploads/signatures if test ! -f $(call SIGNATURE_FUNCTION,$@) ; then \ $(MAKE) $(subst cached,unlocked,$@) \ touch $(call SIGNATURE_FUNCTION,$@) ; fi -- 1.5.6.3 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: unable to make doc
Le 10/06/2009 01:18, Graham Percival disait : On Tue, Jun 09, 2009 at 09:29:57PM +0200, Jean-Charles Malahieude wrote: The two corresponding files might be input/regression/profile-property-access.ly input/lsr/utf-8.ly Those two files include non-Western fonts (such as Hebrew and Japanese). Do you have all the extra (international) fonts installed? input/regression/utf-8.ly includes a list of required packages from a few linux distributions, so if you're on that, take a look at those comments. I'm not certain that they're up-to-date, though -- and yes, this info should be clearly in the Install docs. I'll get to that in a few weeks. Sorry to seem to bother again but, according to the list of packages dealing with fonts which are installed (cf. installed-fonts-pkgs.txt) and what I *see* when opening /home/jcharles/GIT/Mentors/out/lybook-db/4e/lily-7d242e8d.ly with gedit (except that I consider to be erroneous to have an opening brace closing the Hebrew lyrics), I consider the problem I get has nothing to do as regard to fonts. All other dependencies are installed. According to the logs, two others files crash at the same moment, still seeming correct as *.ly in the out/lybook-db subdirectories, get a white eps and pdf output. Both of them reside in input/regression: spanner-break-beyond-parent and profile-property-access and I don't know where they belong in the final documentation. Since I'm really not skilled in autopsy, please examine my log-file. Thanks in advance, Jean-Charles libXfont-1.3.3-1.fc10.i386 lohit-fonts-hindi-2.3.1-1.fc10.noarch urw-fonts-2.4-6.fc10.noarch libfontenc-devel-1.0.4-6.fc10.i386 dejavu-fonts-experimental-2.26-2.fc10.noarch thaifonts-scalable-0.4.9-3.fc9.noarch fontpackages-filesystem-1.20-1.fc10.noarch liberation-fonts-1.04.92-1.fc10.noarch sazanami-fonts-mincho-0.20040629-4.20061016.fc8.noarch lklug-fonts-0.2.2-6.fc10.noarch lohit-fonts-oriya-2.3.1-1.fc10.noarch fontconfig-2.6.0-3.fc10.i386 cjkunifonts-uming-0.2.20080216.1-11.fc10.noarch libfonts-0.3.4-1.fc10.i386 jomolhari-fonts-0.003-5.fc10.noarch khmeros-fonts-base-5.0-3.fc10.noarch vlgothic-fonts-common-20090422-1.fc10.noarch padauk-fonts-2.4-2.fc10.noarch stix-fonts-0.9-7.fc10.noarch lohit-fonts-telugu-2.3.1-1.fc10.noarch japanese-bitmap-fonts-0.20080710-1.fc10.noarch texlive-texmf-errata-fonts-2007-4.fc9.noarch paktype-fonts-2.0-2.fc8.noarch smc-fonts-meera-04.1-1.fc10.noarch xorg-x11-font-utils-7.2-6.fc10.i386 texlive-texmf-fonts-2007-26.fc10.noarch tetex-font-cm-lgc-0.5-10.fc10.noarch taipeifonts-1.2-5.fc9.noarch xorg-x11-fonts-cyrillic-7.2-6.fc9.noarch libfontenc-1.0.4-6.fc10.i386 dejavu-fonts-2.26-2.fc10.noarch lohit-fonts-bengali-2.3.1-1.fc10.noarch abyssinica-fonts-1.0-2.fc8.noarch lohit-fonts-gujarati-2.3.1-1.fc10.noarch fontforge-20090408-2jc.fc10.i386 xorg-x11-fonts-misc-7.2-6.fc9.noarch xorg-x11-fonts-ISO8859-1-75dpi-7.2-6.fc9.noarch kacst-fonts-2.0-1.fc10.noarch lohit-fonts-kannada-2.3.1-1.fc10.noarch fontconfig-devel-2.6.0-3.fc10.i386 libXfont-devel-1.3.3-1.fc10.i386 xorg-x11-fonts-75dpi-7.2-6.fc9.noarch xorg-x11-fonts-Type1-7.2-6.fc9.noarch lohit-fonts-tamil-2.3.1-1.fc10.noarch lohit-fonts-maithili-2.3.1-1.fc10.noarch xorg-x11-fonts-ISO8859-15-100dpi-7.2-6.fc9.noarch vlgothic-fonts-20090422-1.fc10.noarch freefont-20080323-1.fc10.noarch un-core-fonts-dotum-1.0.2-0.6.080608.fc10.noarch lohit-fonts-punjabi-2.3.1-1.fc10.noarch ghostscript-fonts-5.50-19.fc10.noarch bitmap-fonts-0.3-6.fc10.noarch culmus-fonts-0.101-5.fc10.noarch -*- mode: compilation; default-directory: ~/GIT/Mentors/ -*- Compilation started at Thu Jun 11 19:46:49 make doc make --no-builtin-rules -C ./scripts/build out= make[1]: Entering directory `/home/jcharles/GIT/Mentors/scripts/build' true make[1]: Leaving directory `/home/jcharles/GIT/Mentors/scripts/build' make --no-builtin-rules out=www WWW-1 make[1]: Entering directory `/home/jcharles/GIT/Mentors' make PACKAGE=LILYPOND package=lilypond -C python WWW-1 make PACKAGE=LILYPOND package=lilypond -C scripts WWW-1 make PACKAGE=LILYPOND package=lilypond -C flower WWW-1 make PACKAGE=LILYPOND package=lilypond -C lily WWW-1 make PACKAGE=LILYPOND package=lilypond -C mf WWW-1 make PACKAGE=LILYPOND package=lilypond -C ly WWW-1 make PACKAGE=LILYPOND package=lilypond -C tex WWW-1 make PACKAGE=LILYPOND package=lilypond -C ps WWW-1 make PACKAGE=LILYPOND package=lilypond -C scm WWW-1 make PACKAGE=LILYPOND package=lilypond -C po WWW-1 make PACKAGE=LILYPOND package=lilypond -C make WWW-1 make PACKAGE=LILYPOND package=lilypond -C elisp WWW-1 make PACKAGE=LILYPOND package=lilypond -C vim WWW-1 make PACKAGE=LILYPOND package=lilypond -C input WWW-1 make PACKAGE=LILYPOND package=lilypond -C stepmake WWW-1 make PACKAGE=LILYPOND package=lilypond -C Documentation WWW-1 true make[2]: Entering directory `/home/jcharles/GIT/Mentors/python' make PACKAGE=LILYPOND package=lilypond -C auxiliar WWW-1 true make[3]: Entering directory
Re: unable to make doc
On Thu, Jun 11, 2009 at 09:12:08PM +0200, Jean-Charles Malahieude wrote: GPL Ghostscript 8.63 (2008-08-01) Hmm. I'm using ghostscript 8.62 and building correctly. GUB was recently updated to use 8.65. ... actually, that's a thought. Can you compile these failing files if you use the GUB binary? Error: /limitcheck in --string-- Operand stack: --nostringval-- 44 87334 Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop 1904 1 3 %oparray_pop --nostringval-- 1888 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- %loop_continue --nostringval-- 1 --nostringval-- --nostringval-- false 1 %stopped_push --nostringval-- --nostringval-- --nostringval-- --nostringval-- Dictionary stack: --dict:1153/1684(ro)(G)-- --dict:0/20(G)-- --dict:75/200(L)-- --dict:40/50(ro)(G)-- --dict:48/80(L)-- Current allocation mode is local Current file position is 896 Sorry, this is beyond me. :( Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: development on windows
Bertalan Fodor (LilyPondTool) wrote: The goal of this iso to make it usable on a virtualization tool. The open source Sun VirtualBox can for example mount this as the virtual hard disk. Once it's ready maybe I can create a torrent? I've never done that before but it's probably the best way to transfer it. It'll take a while. I can also give you FTP access to one of the servers run by me where you could upload it. That would be the easiest. Success! Ok here's what I have: lilybuntu.iso (717 MB) It's based on standard Ubuntu 9.04 with GNOME desktop environment. I figured this would be the most user-friendly interface for Linux newbies. Almost all desktop applications have been removed. The only big one left is Firefox. It has Gedit, nano, or vim-tiny text editors, Evince document viewer, gnome-terminal, and the nice GUIs for package management and all repos enabled if users want to install anything else. It has all dependencies necessary to build Lilypond and the Documentation, including texi2html 1.82, which I compiled myself and is a few versions newer than what's available in the Ubuntu repo. I tried hard to get it under 700 MB but couldn't get it there. I got it down to 717 from 853 by removing all the texlive documentation (I didn't realize that for every package texlive-foo it was also installing texlive-foo-doc). After making the .iso I tested it in Sun VirtualBox OSE and everything worked perfectly. Here are the exact steps I followed (see if you think they're noob-friendly enough): 1. Install the OS in VirtualBox, then restart the virtual machine and log in 2. open a terminal 3. open firefox 4. Get lilypond source code from git by copying the terminal commands in CG (have to use Ctrl+Shift+V to paste into terminal) 5. run ./autogen.sh, then make all and sudo make install 6. cd Documentation/user 7. make doc 8. use Evince to view pdf output It took a while for everything to build since I only allocated 384 Mb of RAM to the VM, but it worked flawlessly. Bert, if you send me ftp login info privately I can upload it to your server. Maybe I can do it at the office in evening hours and it'll go a lot faster. I only have 256K upload speed at home. :( Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: development on windows
On Thu, Jun 11, 2009 at 05:50:15PM -0500, Jonathan Kulp wrote: Success! Ok here's what I have: lilybuntu.iso (717 MB) And what's that when you gzip or bzip2 it? This could potentially cut the network transfer by more than half. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: development on windows
Hi, On Thu, 11 Jun 2009, Graham Percival wrote: On Thu, Jun 11, 2009 at 05:50:15PM -0500, Jonathan Kulp wrote: Success! Ok here's what I have: lilybuntu.iso (717 MB) And what's that when you gzip or bzip2 it? This could potentially cut the network transfer by more than half. Unlikely: most ways to make a Linux live CD compress the real filesystem using cloop (http://en.wikipedia.org/wiki/Cloop) or something similar. Ciao, Dscho ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: development on windows
Graham Percival wrote: On Thu, Jun 11, 2009 at 05:50:15PM -0500, Jonathan Kulp wrote: Success! Ok here's what I have: lilybuntu.iso (717 MB) And what's that when you gzip or bzip2 it? This could potentially cut the network transfer by more than half. Cheers, - Graham I did bzip2 without any flags and it compressed to 710 MB--not really worth the trouble of having to decompress on the receiving end. Same result with standard zip. I think this thing is already pretty compressed. When remastersys is creating the .iso, it runs a program called squash, (I think that's what it's called) which is why it's only 717 MB instead of the 2.7 GB that it becomes when installed on the hard drive. Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [trivial patch] GUB avoid warning message
LGTM. On Thu, Jun 11, 2009 at 2:31 PM, Graham Percivalgra...@percival-music.ca wrote: Trivial patch to avoid so much clutter in the log files. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel -- 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
