Re: Compiling lilypond in emacs etc
Andrew Bernard writes: > What is the best way to add flags and options to the lilypond compile > command in the emacs lilypond mode? I use M-x compile RET for that. > Also, regarding the failure to widen the buffer after the narrowing > that takes place in certain cases, I see in the archives the > suggestion to wrap the instances of narrow-to-region in a > save-restriction block. Is that the proper solution? Depends on the code, of course. > And if so, why can't this be incorporated into the lilypond emacs code > in the distribution builds? Somebody has to do it. Things still don't happen by magic. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling LilyPond on Linux Mint 19.1
On 20.12.18 12:21, Lukas-Fabian Moser wrote: Folks, this is mostly to give a reference to those who might hit the same problems that I had: I decided to switch from my ancient Linux Mint 17.3 to Linux Mint 19.1 yesterday. In order to set up a working build environment, I had to provide a working Guile 1.8 which seems not to be in the repositories any more. Have a look at the build script attached to https://lists.gnu.org/archive/html/bug-lilypond/2017-08/msg00038.html Knut ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling LilyPond on Linux Mint 19.1
On Fri, Dec 21, 2018 at 07:06:43PM +0100, Urs Liska wrote: > > Am 21.12.18 um 09:06 schrieb Urs Liska: > > Hi Lukas, > > > > thanks for putting this together. Indeed since installing a distro > > that doesn't Guile 1.8 anymore I hadn't been able to compile > > LilyPond anymore. Once I managed to compile Guile 1.8 and do a build > > but for some reason I lost this option. I think the point was that > > after compiling Guile I had to actually change the way LilyPond's > > make was handled - which of course isn't sustainable. Some time ago I ran into the same problem with Guile 1.8 no longer being the default version of Guile in my distro (and in fact, not even installable anymore from the official repo), but Lilypond does not work with newer versions of Guile. Furthermore, Python 2.7 is also no longer the default in my distro, which is an added level of pain, though luckily I can still install Python 2.7, it's just not the default Python that would get invoked. Fortunately, I can compile my own version of Guile 1.8 as you did. Once that is done, I found that I actually don't need to change LilyPond's makefile; all I needed was to set $PATH and re-run LilyPond's autogen.sh with the appropriate customizations, like this: PATH=/usr/src/guile-1.8/bin:$PATH ./autogen.sh \ --with-python-include=/usr/include/python2.7/ \ CFLAGS="-Wno-sequence-point" \ LDFLAGS="-Wl,-rpath,/usr/src/guile-1.8/lib" Of course, replace /usr/src/guile-1.8 with the path to wherever you compiled Guile 1.8 (you don't actually need to install Guile 1.8 anywhere on your system; autogen.sh appeared smart enough to pick up the right files from Guile's source directory once that's built, and once you hacked $PATH to pick up Guile 1.8 before anything else); and replace /usr/include/python2.7 with wherever your distro installed Python 2.7's include files. After running this step, you should be able to just run make as usual, and it should be able to build Lilypond successfully. (I have put the above autogen.sh invocation in a script that I keep with my lilypond git clone, so that I don't have to type all of that every time! Though, truth be told, you really only need to re-run autogen.sh if you have a fresh git clone / source download, or you did a deep cleaning of the source tree. I found that I could still just run make after `git pull` without needing to run autogen.sh again.) Hope this info helps. T -- Leather is waterproof. Ever see a cow with an umbrella? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling LilyPond on Linux Mint 19.1
Am 21.12.18 um 09:06 schrieb Urs Liska: Hi Lukas, thanks for putting this together. Indeed since installing a distro that doesn't Guile 1.8 anymore I hadn't been able to compile LilyPond anymore. Once I managed to compile Guile 1.8 and do a build but for some reason I lost this option. I think the point was that after compiling Guile I had to actually change the way LilyPond's make was handled - which of course isn't sustainable. I'm also running Linux Mint 19.1, and followed your command list (and the previous instructions from the CG). Except that I already had some of the dependencies installed everything worked flawlessly, and I could run a make to compile LilyPond, register that in Frescobaldi and compile a .ly file with it. A warning about missing URW fonts was the only issue I encountered. make doc took the expected ages but worked without errors too! So I can confirm that the steps work on Linux Mint 19. Janek Wachoł has written a few scripts to help managing multiple LilyPond builds, which I really appreciated when I had them working. Basically they provide a configuration layer around the compilation, then create a local clone of the main code repository and build from that copy. That makes it possible to have multiple different builds from different branches (or even states of a branch) in parallel. I will see if I can integrate that with compiling through a self-compiled Guile and report back. Maybe these scripts are of use for others as well. I have looked again into these scripts and found that they (still) work well. The script that I suggest looking into is located at https://github.com/jan-warchol/cli-tools/blob/master/lilypond/build-lily.sh However, when it is considered of general use I'll ask Janek to extract the script from his scripts collection. In order to use the script two environment variables have to be exported (presumably from .bashrc): LILYPOND_GIT=/path/to/lilypond/source/repository LILYPOND_BUILD_DIR=/path/to/root/of/lilypond-builds When invoked without arguments the script will clone the source repository in its current state to the "current" subdirectory of LILYPOND_BUILD_DIR and build it from there. Settings to build other branches (or combinations of branches) to other target directories are described at the beginning of the script. Does this look interesting to anybody? Urs Best Urs Am 20.12.18 um 12:21 schrieb Lukas-Fabian Moser: Folks, this is mostly to give a reference to those who might hit the same problems that I had: I decided to switch from my ancient Linux Mint 17.3 to Linux Mint 19.1 yesterday. In order to set up a working build environment, I had to provide a working Guile 1.8 which seems not to be in the repositories any more. So in addition to following the instructions given in http://lilypond.org/doc/v2.19/Documentation/contributor/requirements-for-compiling-lilypond#linux-mint I also followed the most recent one of the various variations of steps for compiling Guile 1.8 that Federico Bruni gave in October 2017 (http://lilypond.1069038.n5.nabble.com/compiling-lilypond-in-debian-stretch-with-self-compiled-guile-1-8-td206683.html) git clone https://git.savannah.gnu.org/git/guile.git cd guile git checkout branch_release-1-8 ./autogen.sh ./configure --disable-error-on-warning --prefix=/usr/local make sudo make install sudo ldconfig echo "GUILE_CONFIG=/usr/local/bin/guile-config" >> ~/.bashrc Then, after restarting Bash, I could proceed to http://lilypond.org/doc/v2.19/Documentation/contributor/configuring-make and successfully compile current Master. (On my system, the echo [...] >> ~/.bashrc command added the given line without any new-line or whitespace, so I had to insert a newline in an editor.) Probably these instructions would need some more testing/polishing/adjusting to other distributions before they could reasonably be added to the Contributor's Guide, so I just thought it might be helpful to collect them once more here. (In fact I did run into a bit of trouble tonight, but this seems to have been because I wanted to re-use my old lilypond git directory which had been used for compiling on my old system, so it wasn't really a clean start. This might also mean my procedure can't be guaranteed to work on a really fresh Lilypond git folder, but I think they should - I removed the old build/ folder before the first succesful compile, so there shouldn't have been any remnants of earlier successful compilations.) Or would there have been a much easier way to success? (The upside for me: Now I have the necessary Python/Qt/Lilypond bindings to also run current Frescobaldi from the git repository following Urs's excellent instructions on https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-on-Linux.) Best Lukas ___ lilypond-user mailing list lilypond-user@gnu.org
Re: Compiling LilyPond on Linux Mint 19.1
Hi Federico and Lukas, Am 21.12.18 um 09:59 schrieb Federico Bruni: Il giorno ven 21 dic 2018 alle 9:06, Urs Liska ha scritto: [...] A warning about missing URW fonts was the only issue I encountered. make doc took the expected ages but worked without errors too! So I can confirm that the steps work on Linux Mint 19. Hi Urs this was discussed before but you might have missed it. You can use part of this script: https://github.com/fedelibre/LilyDevOS/blob/master/mkosi/debian/mkosi.extra/etc/skel/setup.sh#L39 to download the needed .otf files. AFAIK, only Fedora (?) includes .otf files in its URW fonts package, because I asked for it: https://bugzilla.redhat.com/show_bug.cgi?id=1496466#c18 Thanks, this seems to have worked. Fedora packager wrote that OTF files are not too big and decided that they can be distributed along with .t1 and .afm files. If somebody asked Debian to do the same for fonts-urw-base35 package, above script would be not necessary anymore - for Debian nor its derivatives (Ubuntu, Mint, etc.). But until that happens this information should be added to any CG. Although if I'm not mistaken this is not related to the "Linux Mint" part of the section, isn't it? Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling LilyPond on Linux Mint 19.1
Il giorno ven 21 dic 2018 alle 9:06, Urs Liska ha scritto: [...] A warning about missing URW fonts was the only issue I encountered. make doc took the expected ages but worked without errors too! So I can confirm that the steps work on Linux Mint 19. Hi Urs this was discussed before but you might have missed it. You can use part of this script: https://github.com/fedelibre/LilyDevOS/blob/master/mkosi/debian/mkosi.extra/etc/skel/setup.sh#L39 to download the needed .otf files. AFAIK, only Fedora (?) includes .otf files in its URW fonts package, because I asked for it: https://bugzilla.redhat.com/show_bug.cgi?id=1496466#c18 Fedora packager wrote that OTF files are not too big and decided that they can be distributed along with .t1 and .afm files. If somebody asked Debian to do the same for fonts-urw-base35 package, above script would be not necessary anymore - for Debian nor its derivatives (Ubuntu, Mint, etc.). ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling LilyPond on Linux Mint 19.1
Hi Lukas, thanks for putting this together. Indeed since installing a distro that doesn't Guile 1.8 anymore I hadn't been able to compile LilyPond anymore. Once I managed to compile Guile 1.8 and do a build but for some reason I lost this option. I think the point was that after compiling Guile I had to actually change the way LilyPond's make was handled - which of course isn't sustainable. I'm also running Linux Mint 19.1, and followed your command list (and the previous instructions from the CG). Except that I already had some of the dependencies installed everything worked flawlessly, and I could run a make to compile LilyPond, register that in Frescobaldi and compile a .ly file with it. A warning about missing URW fonts was the only issue I encountered. make doc took the expected ages but worked without errors too! So I can confirm that the steps work on Linux Mint 19. Janek Wachoł has written a few scripts to help managing multiple LilyPond builds, which I really appreciated when I had them working. Basically they provide a configuration layer around the compilation, then create a local clone of the main code repository and build from that copy. That makes it possible to have multiple different builds from different branches (or even states of a branch) in parallel. I will see if I can integrate that with compiling through a self-compiled Guile and report back. Maybe these scripts are of use for others as well. Best Urs Am 20.12.18 um 12:21 schrieb Lukas-Fabian Moser: Folks, this is mostly to give a reference to those who might hit the same problems that I had: I decided to switch from my ancient Linux Mint 17.3 to Linux Mint 19.1 yesterday. In order to set up a working build environment, I had to provide a working Guile 1.8 which seems not to be in the repositories any more. So in addition to following the instructions given in http://lilypond.org/doc/v2.19/Documentation/contributor/requirements-for-compiling-lilypond#linux-mint I also followed the most recent one of the various variations of steps for compiling Guile 1.8 that Federico Bruni gave in October 2017 (http://lilypond.1069038.n5.nabble.com/compiling-lilypond-in-debian-stretch-with-self-compiled-guile-1-8-td206683.html) git clone https://git.savannah.gnu.org/git/guile.git cd guile git checkout branch_release-1-8 ./autogen.sh ./configure --disable-error-on-warning --prefix=/usr/local make sudo make install sudo ldconfig echo "GUILE_CONFIG=/usr/local/bin/guile-config" >> ~/.bashrc Then, after restarting Bash, I could proceed to http://lilypond.org/doc/v2.19/Documentation/contributor/configuring-make and successfully compile current Master. (On my system, the echo [...] >> ~/.bashrc command added the given line without any new-line or whitespace, so I had to insert a newline in an editor.) Probably these instructions would need some more testing/polishing/adjusting to other distributions before they could reasonably be added to the Contributor's Guide, so I just thought it might be helpful to collect them once more here. (In fact I did run into a bit of trouble tonight, but this seems to have been because I wanted to re-use my old lilypond git directory which had been used for compiling on my old system, so it wasn't really a clean start. This might also mean my procedure can't be guaranteed to work on a really fresh Lilypond git folder, but I think they should - I removed the old build/ folder before the first succesful compile, so there shouldn't have been any remnants of earlier successful compilations.) Or would there have been a much easier way to success? (The upside for me: Now I have the necessary Python/Qt/Lilypond bindings to also run current Frescobaldi from the git repository following Urs's excellent instructions on https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-on-Linux.) Best Lukas ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling lilypond
Op dinsdag 29 mei 2007, schreef Thomas Gollenia: Hi, When I tried to compile lilypond (all dependencies should be solved) it came up with the following error message: chmod 755 out/lilypond-invoke-editor /usr/bin/perl /Users/Thommy/Documents/Downloads/lilypond-2.10.25/ buildscripts/out/help2man out/lilypond-invoke-editor out/lilypond- invoke-editor.1 help2man: can't get `--help' info from out/lilypond-invoke-editor make[1]: *** [out/lilypond-invoke-editor.1] Error 1 make: *** [all] Error 2 I got the same problem. I found the solution by executing scripts/out/lilypond-invoke-editor by hand, which showed that guile could not execute that script because it had been built without regexp support. Right now I'm recompiling guile with regexp support (--enable-regex). best regards, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ You must be the change you wish to see in the world. -- Mahatma Gandi ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling lilypond files from Mutopia
On May 27, 2006, at 8:17 AM, Peter Clarke wrote: Dear list, I would like to compile a Lilypond file downloaded from Mutopia. It needs an include file (paper-20.ly). Where can I get this? And does that define all the 'extra' syntax the .ly file seems to contain? Thanks, Peter C Unfortunately, there is no simple way for the Mutopia maintainer (Chris Sawer) to update all the files with each new Lilypond version. I would suggest using the latest stable Lilypond version's convert-ly to update the file. If you can download one of the compiled binary Lilypond versions, use the convert function. Depending on how old is the Lilypond version of the Mutopia file, you may have to do some further editing. Regards, Stan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling Lilypond-2.6.0 On Gentoo
On Fri, 2005-07-01 at 21:59 -0700, Daniel Johnson wrote: If you are going to be building the documentation on Gentoo (i.e. you have doc in your USE variable) it is almost imperative that you use a version of Guile newer than the latest stable -- use a CVS snapshot of the development branch, and you get Han-Wen's garbage-collection patches. What I wound up doing was the following (as root): Thanks for the advice, Daniel, I'll remember that if I try to compile the documentation. I did, however, solve the original problem I was having. I recompiled tetex, and swapped autotrace for potrace. I'm not sure which of the two was the culprit, but lilypond 2.6 compiled and is running fine now. Thanks for the help, Scott -- Oh, people can come up with statistics to prove anything. 14% of people know that. -- Homer Simpson ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling Lilypond-2.6.0 On Gentoo
If this list allows .tar.bz2 attachments, you could try unpacking the attachment into your $PORTDIR_OVERLAY directory. It adds ebuilds for the correct versions of mftrace and fontforge, so it should help resolve any dependency problems. Joe lilypond-ebuild.tar.bz2 Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling Lilypond-2.6.0 On Gentoo
Joe Neeman wrote: If this list allows .tar.bz2 attachments, you could try unpacking the attachment into your $PORTDIR_OVERLAY directory. It adds ebuilds for the correct versions of mftrace and fontforge, so it should help resolve any dependency problems. Joe Hi Joe, Thanks for taking the time to respond! I believe I am using the same versions of mftrace and fontforge as you have so kindly provided me with. I suspect the problem may be an environmental variable of some sort. Nonetheless, I'll give these ebuilds a go and see how things progress. Thanks again, Scott ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling Lilypond-2.6.0 On Gentoo
If you are going to be building the documentation on Gentoo (i.e. you have doc in your USE variable) it is almost imperative that you use a version of Guile newer than the latest stable -- use a CVS snapshot of the development branch, and you get Han-Wen's garbage-collection patches. What I wound up doing was the following (as root): ***WARNING: UGLY HACKS*** 1. cd ~ 2. wget ftp://ftp.dt.e-technik.uni-dortmund.de/pub/guile/snapshots/guile-core.unstable.tar.gz 3. tar xzf guile-core.unstable.tar.gz 4. tar czf guile-1.7.2.tar.gz guile-core.unstable* 5. mv guile-1.7.2.tar.gz /usr/portage/distfiles 6. mkdir -p $PORTDIR_OVERLAY/dev-util/guile/ 7. cd $PORTDIR_OVERLAY/dev-util/guile 8. cp /usr/portage/dev-util/guile-1.6.8.ebuild ./guile-1.7.2.ebuild 9. edit guile-1.7.2.ebuild. Add dev-libs/gmp to the DEPEND var. Remove the line that patches in case of GCC 4.0 (unless you are running GCC 4, in which case you'll have to figure out how to modify the patch yourself) 10. ebuild guile-1.7.2.ebuild digest 11. emerge guile 12. cd $PORTDIR_OVERLAY/media-sound/lilypond 13. edit lilypond-2.6.0.ebuild. In the src_install function, comment out the entire if use doc; block. 14. ebuild lilypond-2.6.0.ebuild digest 15. mkdir -p /var/tmp/portage/lilypond-2.6.0/work 16. USE=doc FEATURES=keepwork emerge lilypond 17. mkdir -p /usr/share/doc/lilypond; cd /usr/share/doc/lilypond 18. tar xzf /var/tmp/portage/lilypond-2.6.0/work/lilypond-2.6.0/out-www/web.tar.gz I'm sure there are better ways of doing this but this was my quick dirty method. Building of documentation proceeded at a very nice pace, and didn't crash like it has been doing for the last month or so. This should also help users who are building massive documents with lilypond-book. I sure hope the Gentoo team supports this stuff without my hacks soon... but that's unlikely since they seem to be stalled on creating an ESP Ghostscript 8.15rc3 ebuild. And forget about Guile CVS... development and release of Guile seems to happen at a snail's pace, and I don't think anyone other than Han-Wen has placed any importance on the GC portion of Guile. We are *so* spoiled with the pace of Lilypond development! --Daniel Joe Neeman wrote: If this list allows .tar.bz2 attachments, you could try unpacking the attachment into your $PORTDIR_OVERLAY directory. It adds ebuilds for the correct versions of mftrace and fontforge, so it should help resolve any dependency problems. Joe ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling Lilypond...
J. L. writes: Which ec-fonts-mftraced package does Cygwin need to use? Any of http://lilypond.org/download/fonts/ http://lilypond.org/cygwin/uploads/ec-fonts-mftraced Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: compiling lilypond
I'm pretty sure I have it installed; when I type mf at the prompt I get: This is METAFONT, Version 2.7182 (Web2C 7.4.5) ** I have the files mf and mfw in /usr/share/texmf/bin Configure detects everything automatically except kpathsea, which is installed in the default directory /usr/share/texmf/(lib; include) and does not complain after typing export LDFLAGS. etc. It does tell me to please consider installing optional programs: kpsewhich, (how would I do that?) Also, maybe I'm doing something really stupid, because I'm a bit of a linux newbie. Anyway, thanks for your help ( congrats on the new release!), David --- Jan Nieuwenhuizen [EMAIL PROTECTED] wrote: sdf sdfs writes: make[1]: Entering directory `/home/david/lilypond-2.4.0/mf' echo mf mfont not found \mode:=laserjet; nonstopmode; You should install metafont, probably in the tetex package. I'm surprised that configure did not complain about metafont. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org __ Post your free ad now! http://personals.yahoo.ca ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling Lilypond-2.3.11 on Slackware 10
Finally it worked!
In Slackware 10 keeping lilypond-profile.sh in /etc/profile.d/ does not
work. To make it work I did the following:
Copied buildcripts/out/lilypond-profile to /usr/bin
Then, I appended the following line:
source /usr/bin/lilypond-profile
to the end of /etc/profile. Logout and login. Now Lilypond-2.3.11 is
working fine. Strangely, this is working even for csh without using
lilypond-login.
Thanks Mr. Mats Bengtsson for your patient help.
Anand
On 08/18/2004 08:37:35 PM, Mats Bengtsson wrote:
OK, now you have managed to source the file.
However, it seems that your installation of teTeX doesn't
behave as it should.
What does the following sequence of commands return?
unset TEXMF
kpsexpand \$TEXMF
kpsewhich texmf.cnf
Also, you should try to figure out why you didn't manage to
source the file earlier.
/Mats
R S Ananda Murthy wrote:
On 08/18/2004 06:48:28 PM, Mats Bengtsson wrote:
First of all, I hope that we are talking about the file
buildscripts/out/lilypond-profile
and NOT
buildscripts/lilypond-profile.sh
To help us understand what's going on, try the following:
- Go to the lilypond-* directory where you run the compilation
- Run the command
set -x
this will make bash echo every line it executes
- Run (I hope you have noted the initial dot followed by a space)
. buildscripts/out/lilypond-profile
I was missing the starting . and space!
- Reset bash to normal behaviour by running
set +x
Send the resulting output to the mailing list.
/Mats
This is the resulting output:
+ . buildscripts/out/lilypond-profile
++ '[' -n '' ']'
+++ basename bash
++ '[' -z '' -a bash = lilypond-profile ']'
++ '[' -z '' ']'
+++ echo /usr/share/lilypond/2.3.11
+++ sed 's!//!/!g'
++ datadir=/usr/share/lilypond/2.3.11
+++ echo '{/usr/share/lilypond/2.3.11,}'
+++ grep /usr/share/lilypond/2.3.11
++ '[' -z '{/usr/share/lilypond/2.3.11,}' ']'
After this if I now type the command printenv TEXMF I get:
+ printenv TEXMF
{/usr/share/lilypond/2.3.11,}
Anand
R S Ananda Murthy wrote:
On 08/18/2004 01:48:08 PM, Mats Bengtsson wrote:
I'm cross-posting to lilypond-user, to increase the chance
that you get help from some Slackware user.
R S Ananda Murthy wrote:
On 08/17/2004 08:45:10 PM, Mats Bengtsson wrote:
Did you start a new shell first?
Yes.
I was wrong, you probably have to logout/login again to
make bash read the profile files. Hopefully this helps
What does the following command return:
printenv TEXMF
Nothing.
Which indicates that the lilypond-profile file wasn't
read.
If you are eager to get started (waiting for some Slackware
user on the list to provide more help), just run
. /.../lilypond-profile
in the shell where you want to run LilyPond.
I did this after making lilypond-profile executable. But after
this, if I do printenv TEXMF I get nothing. So, I feel there is
something wrong in lilypond-profile. I think, if this is set
right, Lilypond- 2.3.11 may work properly on Slackware 10.
In another mail, you wrote
Hello,
While invoking Lilypond, what sould be the following environment
variables:
TEXMF
LILYPONDPREFIX
LANG
How to set these variables? Can anybody give some examples?
If you did 'make install', you should leave LILYPONDPREFIX unset.
The same goes for LANG, unless you want your programs to speak
some other language than english. If you try to set the TEXMF
variable yourself, it's very likely to get wrong, that's why
we have the lilypond-profile file.
/Mats
R S Ananda Murthy wrote:
On 08/17/2004 08:07:33 PM, R S Ananda Murthy wrote:
I am hereby placing this discussion in the mailing list.
Anand
On 08/17/2004 03:51:01 PM, Mats Bengtsson wrote:
Please keep the discussion on the mailing list, for the
benefit of yourself since you get access to the collected
expertise on the list and for the benefit of others who
experience
similar problems. Feel free to quote my answer below if you
wish.
R S Ananda Murthy wrote:
Hello,
Thanks for your mail. Now Lilypond-2.3.11 is running on
Slackware 10! I installed mftraced ec fonts. I have done
texhash. But when I do
lilypond test.py
I get the following message:
Now processing `test.ly'
Parsing...
Interpreting music... error: can't find `feta20.afm'
Music font has not been installed properly. Aborting
I have not understood what I should do with the scripts
lilypond-profile
lilypond-login
I am using bash. Could you please help.
I don't know how things are setup in Slackware. On RedHat
systems,
there's a directory /etc/profile.d/, where you can put the
file
lilypond-profile (renamed to lilypond-profile.sh) so it will
be
automatically read as soon as you start a new shell.
Otherwise, you can add a line
. /whatever/path/to/the/file/lilypond-profile
in your own ~/.profile
/Mats
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello,
As mentioned above, I copied lilypond-profile.sh into /etc/
profile. d.
Re: Compiling Lilypond-2.3.11 on Slackware 10
I'm cross-posting to lilypond-user, to increase the chance
that you get help from some Slackware user.
R S Ananda Murthy wrote:
On 08/17/2004 08:45:10 PM, Mats Bengtsson wrote:
Did you start a new shell first?
Yes.
I was wrong, you probably have to logout/login again to
make bash read the profile files. Hopefully this helps
What does the following command return:
printenv TEXMF
Nothing.
Which indicates that the lilypond-profile file wasn't
read.
If you are eager to get started (waiting for some Slackware
user on the list to provide more help), just run
. /.../lilypond-profile
in the shell where you want to run LilyPond.
In another mail, you wrote
Hello,
While invoking Lilypond, what sould be the following environment
variables:
TEXMF
LILYPONDPREFIX
LANG
How to set these variables? Can anybody give some examples?
If you did 'make install', you should leave LILYPONDPREFIX unset.
The same goes for LANG, unless you want your programs to speak
some other language than english. If you try to set the TEXMF
variable yourself, it's very likely to get wrong, that's why
we have the lilypond-profile file.
/Mats
R S Ananda Murthy wrote:
On 08/17/2004 08:07:33 PM, R S Ananda Murthy wrote:
I am hereby placing this discussion in the mailing list.
Anand
On 08/17/2004 03:51:01 PM, Mats Bengtsson wrote:
Please keep the discussion on the mailing list, for the
benefit of yourself since you get access to the collected
expertise on the list and for the benefit of others who experience
similar problems. Feel free to quote my answer below if you wish.
R S Ananda Murthy wrote:
Hello,
Thanks for your mail. Now Lilypond-2.3.11 is running on
Slackware 10! I installed mftraced ec fonts. I have done
texhash. But when I do
lilypond test.py
I get the following message:
Now processing `test.ly'
Parsing...
Interpreting music... error: can't find `feta20.afm'
Music font has not been installed properly. Aborting
I have not understood what I should do with the scripts
lilypond-profile
lilypond-login
I am using bash. Could you please help.
I don't know how things are setup in Slackware. On RedHat systems,
there's a directory /etc/profile.d/, where you can put the file
lilypond-profile (renamed to lilypond-profile.sh) so it will be
automatically read as soon as you start a new shell.
Otherwise, you can add a line
. /whatever/path/to/the/file/lilypond-profile
in your own ~/.profile
/Mats
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello,
As mentioned above, I copied lilypond-profile.sh into /etc/profile.
d. In Slackware 10 also we have /etc/profile.d. Now I tried
lilypond test.ly
where the content of test.ly is
{ c'4 e' g' }
But I still get the message:
Now processing `test.ly'
Parsing...
Interpreting music... error: can't find `feta20.afm'
Music font has not been installed properly. Aborting
I have installed mftraced ec fonts and done texhash. What is the
problem?
Anand
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling Lilypond-2.3.11 on Slackware 10
On 08/18/2004 01:48:08 PM, Mats Bengtsson wrote:
I'm cross-posting to lilypond-user, to increase the chance
that you get help from some Slackware user.
R S Ananda Murthy wrote:
On 08/17/2004 08:45:10 PM, Mats Bengtsson wrote:
Did you start a new shell first?
Yes.
I was wrong, you probably have to logout/login again to
make bash read the profile files. Hopefully this helps
What does the following command return:
printenv TEXMF
Nothing.
Which indicates that the lilypond-profile file wasn't
read.
If you are eager to get started (waiting for some Slackware
user on the list to provide more help), just run
. /.../lilypond-profile
in the shell where you want to run LilyPond.
I did this after making lilypond-profile executable. But after this,
if I do printenv TEXMF I get nothing. So, I feel there is something
wrong in lilypond-profile. I think, if this is set right, Lilypond-
2.3.11 may work properly on Slackware 10.
In another mail, you wrote
Hello,
While invoking Lilypond, what sould be the following environment
variables:
TEXMF
LILYPONDPREFIX
LANG
How to set these variables? Can anybody give some examples?
If you did 'make install', you should leave LILYPONDPREFIX unset.
The same goes for LANG, unless you want your programs to speak
some other language than english. If you try to set the TEXMF
variable yourself, it's very likely to get wrong, that's why
we have the lilypond-profile file.
/Mats
R S Ananda Murthy wrote:
On 08/17/2004 08:07:33 PM, R S Ananda Murthy wrote:
I am hereby placing this discussion in the mailing list.
Anand
On 08/17/2004 03:51:01 PM, Mats Bengtsson wrote:
Please keep the discussion on the mailing list, for the
benefit of yourself since you get access to the collected
expertise on the list and for the benefit of others who
experience
similar problems. Feel free to quote my answer below if you
wish.
R S Ananda Murthy wrote:
Hello,
Thanks for your mail. Now Lilypond-2.3.11 is running on
Slackware 10! I installed mftraced ec fonts. I have done
texhash. But when I do
lilypond test.py
I get the following message:
Now processing `test.ly'
Parsing...
Interpreting music... error: can't find `feta20.afm'
Music font has not been installed properly. Aborting
I have not understood what I should do with the scripts
lilypond-profile
lilypond-login
I am using bash. Could you please help.
I don't know how things are setup in Slackware. On RedHat
systems,
there's a directory /etc/profile.d/, where you can put the file
lilypond-profile (renamed to lilypond-profile.sh) so it will be
automatically read as soon as you start a new shell.
Otherwise, you can add a line
. /whatever/path/to/the/file/lilypond-profile
in your own ~/.profile
/Mats
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello,
As mentioned above, I copied lilypond-profile.sh into /etc/
profile. d. In Slackware 10 also we have /etc/profile.d. Now I
tried
lilypond test.ly
where the content of test.ly is
{ c'4 e' g' }
But I still get the message:
Now processing `test.ly'
Parsing...
Interpreting music... error: can't find `feta20.afm'
Music font has not been installed properly. Aborting
I have installed mftraced ec fonts and done texhash. What is the
problem?
Anand
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
-- =
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 Fax: (+46) 8
790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling Lilypond-2.3.11 on Slackware 10
First of all, I hope that we are talking about the file
buildscripts/out/lilypond-profile
and NOT
buildscripts/lilypond-profile.sh
To help us understand what's going on, try the following:
- Go to the lilypond-* directory where you run the compilation
- Run the command
set -x
this will make bash echo every line it executes
- Run (I hope you have noted the initial dot followed by a space)
. buildscripts/out/lilypond-profile
- Reset bash to normal behaviour by running
set +x
Send the resulting output to the mailing list.
/Mats
R S Ananda Murthy wrote:
On 08/18/2004 01:48:08 PM, Mats Bengtsson wrote:
I'm cross-posting to lilypond-user, to increase the chance
that you get help from some Slackware user.
R S Ananda Murthy wrote:
On 08/17/2004 08:45:10 PM, Mats Bengtsson wrote:
Did you start a new shell first?
Yes.
I was wrong, you probably have to logout/login again to
make bash read the profile files. Hopefully this helps
What does the following command return:
printenv TEXMF
Nothing.
Which indicates that the lilypond-profile file wasn't
read.
If you are eager to get started (waiting for some Slackware
user on the list to provide more help), just run
. /.../lilypond-profile
in the shell where you want to run LilyPond.
I did this after making lilypond-profile executable. But after this,
if I do printenv TEXMF I get nothing. So, I feel there is something
wrong in lilypond-profile. I think, if this is set right, Lilypond-
2.3.11 may work properly on Slackware 10.
In another mail, you wrote
Hello,
While invoking Lilypond, what sould be the following environment
variables:
TEXMF
LILYPONDPREFIX
LANG
How to set these variables? Can anybody give some examples?
If you did 'make install', you should leave LILYPONDPREFIX unset.
The same goes for LANG, unless you want your programs to speak
some other language than english. If you try to set the TEXMF
variable yourself, it's very likely to get wrong, that's why
we have the lilypond-profile file.
/Mats
R S Ananda Murthy wrote:
On 08/17/2004 08:07:33 PM, R S Ananda Murthy wrote:
I am hereby placing this discussion in the mailing list.
Anand
On 08/17/2004 03:51:01 PM, Mats Bengtsson wrote:
Please keep the discussion on the mailing list, for the
benefit of yourself since you get access to the collected
expertise on the list and for the benefit of others who experience
similar problems. Feel free to quote my answer below if you wish.
R S Ananda Murthy wrote:
Hello,
Thanks for your mail. Now Lilypond-2.3.11 is running on
Slackware 10! I installed mftraced ec fonts. I have done
texhash. But when I do
lilypond test.py
I get the following message:
Now processing `test.ly'
Parsing...
Interpreting music... error: can't find `feta20.afm'
Music font has not been installed properly. Aborting
I have not understood what I should do with the scripts
lilypond-profile
lilypond-login
I am using bash. Could you please help.
I don't know how things are setup in Slackware. On RedHat systems,
there's a directory /etc/profile.d/, where you can put the file
lilypond-profile (renamed to lilypond-profile.sh) so it will be
automatically read as soon as you start a new shell.
Otherwise, you can add a line
. /whatever/path/to/the/file/lilypond-profile
in your own ~/.profile
/Mats
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello,
As mentioned above, I copied lilypond-profile.sh into /etc/
profile. d. In Slackware 10 also we have /etc/profile.d. Now I tried
lilypond test.ly
where the content of test.ly is
{ c'4 e' g' }
But I still get the message:
Now processing `test.ly'
Parsing...
Interpreting music... error: can't find `feta20.afm'
Music font has not been installed properly. Aborting
I have installed mftraced ec fonts and done texhash. What is the
problem?
Anand
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
-- =
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 Fax: (+46) 8
790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
Re: Compiling Lilypond-2.3.11 on Slackware 10
On 08/18/2004 06:48:28 PM, Mats Bengtsson wrote:
First of all, I hope that we are talking about the file
buildscripts/out/lilypond-profile
and NOT
buildscripts/lilypond-profile.sh
To help us understand what's going on, try the following:
- Go to the lilypond-* directory where you run the compilation
- Run the command
set -x
this will make bash echo every line it executes
- Run (I hope you have noted the initial dot followed by a space)
. buildscripts/out/lilypond-profile
- Reset bash to normal behaviour by running
set +x
Send the resulting output to the mailing list.
/Mats
This is the resulting output:
+ . buildscripts/out/lilypond-profile
++ '[' -n '' ']'
+++ basename bash
++ '[' -z '' -a bash = lilypond-profile ']'
++ '[' -z '' ']'
+++ echo /usr/share/lilypond/2.3.11
+++ sed 's!//!/!g'
++ datadir=/usr/share/lilypond/2.3.11
+++ echo '{/usr/share/lilypond/2.3.11,}'
+++ grep /usr/share/lilypond/2.3.11
++ '[' -z '{/usr/share/lilypond/2.3.11,}' ']'
After this if I now type the command printenv TEXMF I get:
+ printenv TEXMF
{/usr/share/lilypond/2.3.11,}
Anand
R S Ananda Murthy wrote:
On 08/18/2004 01:48:08 PM, Mats Bengtsson wrote:
I'm cross-posting to lilypond-user, to increase the chance
that you get help from some Slackware user.
R S Ananda Murthy wrote:
On 08/17/2004 08:45:10 PM, Mats Bengtsson wrote:
Did you start a new shell first?
Yes.
I was wrong, you probably have to logout/login again to
make bash read the profile files. Hopefully this helps
What does the following command return:
printenv TEXMF
Nothing.
Which indicates that the lilypond-profile file wasn't
read.
If you are eager to get started (waiting for some Slackware
user on the list to provide more help), just run
. /.../lilypond-profile
in the shell where you want to run LilyPond.
I did this after making lilypond-profile executable. But after
this, if I do printenv TEXMF I get nothing. So, I feel there is
something wrong in lilypond-profile. I think, if this is set right,
Lilypond- 2.3.11 may work properly on Slackware 10.
In another mail, you wrote
Hello,
While invoking Lilypond, what sould be the following environment
variables:
TEXMF
LILYPONDPREFIX
LANG
How to set these variables? Can anybody give some examples?
If you did 'make install', you should leave LILYPONDPREFIX unset.
The same goes for LANG, unless you want your programs to speak
some other language than english. If you try to set the TEXMF
variable yourself, it's very likely to get wrong, that's why
we have the lilypond-profile file.
/Mats
R S Ananda Murthy wrote:
On 08/17/2004 08:07:33 PM, R S Ananda Murthy wrote:
I am hereby placing this discussion in the mailing list.
Anand
On 08/17/2004 03:51:01 PM, Mats Bengtsson wrote:
Please keep the discussion on the mailing list, for the
benefit of yourself since you get access to the collected
expertise on the list and for the benefit of others who
experience
similar problems. Feel free to quote my answer below if you
wish.
R S Ananda Murthy wrote:
Hello,
Thanks for your mail. Now Lilypond-2.3.11 is running on
Slackware 10! I installed mftraced ec fonts. I have done
texhash. But when I do
lilypond test.py
I get the following message:
Now processing `test.ly'
Parsing...
Interpreting music... error: can't find `feta20.afm'
Music font has not been installed properly. Aborting
I have not understood what I should do with the scripts
lilypond-profile
lilypond-login
I am using bash. Could you please help.
I don't know how things are setup in Slackware. On RedHat
systems,
there's a directory /etc/profile.d/, where you can put the
file
lilypond-profile (renamed to lilypond-profile.sh) so it will
be
automatically read as soon as you start a new shell.
Otherwise, you can add a line
. /whatever/path/to/the/file/lilypond-profile
in your own ~/.profile
/Mats
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello,
As mentioned above, I copied lilypond-profile.sh into /etc/
profile. d. In Slackware 10 also we have /etc/profile.d. Now I
tried
lilypond test.ly
where the content of test.ly is
{ c'4 e' g' }
But I still get the message:
Now processing `test.ly'
Parsing...
Interpreting music... error: can't find `feta20.afm'
Music font has not been installed properly. Aborting
I have installed mftraced ec fonts and done texhash. What is the
problem?
Anand
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
-- =
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 Fax: (+46) 8
790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
Re: Compiling Lilypond-2.3.11 on Slackware 10
OK, now you have managed to source the file.
However, it seems that your installation of teTeX doesn't
behave as it should.
What does the following sequence of commands return?
unset TEXMF
kpsexpand \$TEXMF
kpsewhich texmf.cnf
Also, you should try to figure out why you didn't manage to
source the file earlier.
/Mats
R S Ananda Murthy wrote:
On 08/18/2004 06:48:28 PM, Mats Bengtsson wrote:
First of all, I hope that we are talking about the file
buildscripts/out/lilypond-profile
and NOT
buildscripts/lilypond-profile.sh
To help us understand what's going on, try the following:
- Go to the lilypond-* directory where you run the compilation
- Run the command
set -x
this will make bash echo every line it executes
- Run (I hope you have noted the initial dot followed by a space)
. buildscripts/out/lilypond-profile
- Reset bash to normal behaviour by running
set +x
Send the resulting output to the mailing list.
/Mats
This is the resulting output:
+ . buildscripts/out/lilypond-profile
++ '[' -n '' ']'
+++ basename bash
++ '[' -z '' -a bash = lilypond-profile ']'
++ '[' -z '' ']'
+++ echo /usr/share/lilypond/2.3.11
+++ sed 's!//!/!g'
++ datadir=/usr/share/lilypond/2.3.11
+++ echo '{/usr/share/lilypond/2.3.11,}'
+++ grep /usr/share/lilypond/2.3.11
++ '[' -z '{/usr/share/lilypond/2.3.11,}' ']'
After this if I now type the command printenv TEXMF I get:
+ printenv TEXMF
{/usr/share/lilypond/2.3.11,}
Anand
R S Ananda Murthy wrote:
On 08/18/2004 01:48:08 PM, Mats Bengtsson wrote:
I'm cross-posting to lilypond-user, to increase the chance
that you get help from some Slackware user.
R S Ananda Murthy wrote:
On 08/17/2004 08:45:10 PM, Mats Bengtsson wrote:
Did you start a new shell first?
Yes.
I was wrong, you probably have to logout/login again to
make bash read the profile files. Hopefully this helps
What does the following command return:
printenv TEXMF
Nothing.
Which indicates that the lilypond-profile file wasn't
read.
If you are eager to get started (waiting for some Slackware
user on the list to provide more help), just run
. /.../lilypond-profile
in the shell where you want to run LilyPond.
I did this after making lilypond-profile executable. But after
this, if I do printenv TEXMF I get nothing. So, I feel there is
something wrong in lilypond-profile. I think, if this is set right,
Lilypond- 2.3.11 may work properly on Slackware 10.
In another mail, you wrote
Hello,
While invoking Lilypond, what sould be the following environment
variables:
TEXMF
LILYPONDPREFIX
LANG
How to set these variables? Can anybody give some examples?
If you did 'make install', you should leave LILYPONDPREFIX unset.
The same goes for LANG, unless you want your programs to speak
some other language than english. If you try to set the TEXMF
variable yourself, it's very likely to get wrong, that's why
we have the lilypond-profile file.
/Mats
R S Ananda Murthy wrote:
On 08/17/2004 08:07:33 PM, R S Ananda Murthy wrote:
I am hereby placing this discussion in the mailing list.
Anand
On 08/17/2004 03:51:01 PM, Mats Bengtsson wrote:
Please keep the discussion on the mailing list, for the
benefit of yourself since you get access to the collected
expertise on the list and for the benefit of others who
experience
similar problems. Feel free to quote my answer below if you
wish.
R S Ananda Murthy wrote:
Hello,
Thanks for your mail. Now Lilypond-2.3.11 is running on
Slackware 10! I installed mftraced ec fonts. I have done
texhash. But when I do
lilypond test.py
I get the following message:
Now processing `test.ly'
Parsing...
Interpreting music... error: can't find `feta20.afm'
Music font has not been installed properly. Aborting
I have not understood what I should do with the scripts
lilypond-profile
lilypond-login
I am using bash. Could you please help.
I don't know how things are setup in Slackware. On RedHat
systems,
there's a directory /etc/profile.d/, where you can put the file
lilypond-profile (renamed to lilypond-profile.sh) so it will be
automatically read as soon as you start a new shell.
Otherwise, you can add a line
. /whatever/path/to/the/file/lilypond-profile
in your own ~/.profile
/Mats
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello,
As mentioned above, I copied lilypond-profile.sh into /etc/
profile. d. In Slackware 10 also we have /etc/profile.d. Now I
tried
lilypond test.ly
where the content of test.ly is
{ c'4 e' g' }
But I still get the message:
Now processing `test.ly'
Parsing...
Interpreting music... error: can't find `feta20.afm'
Music font has not been installed properly. Aborting
I have installed mftraced ec fonts and done texhash. What is
the problem?
Anand
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
RE: Compiling Lilypond 1.7.4
Hi, Many thanks Klaus. My mistake was putting duff information in the e-mail ;) I checked /etc/ld.so.conf and it contained /usr/local/lib. However, running ldconfig cured the problem. I'm not sure what the problem was in the end, but I will look into it a bit more. Up and running! Wahay! Cheers! Ralph -Original Message- From: Klaus Zimmermann [mailto:klaus_zimmermann;gmx.de] Sent: 05 November 2002 22:27 To: Ralph Little Cc: '[EMAIL PROTECTED]' Subject: Re: Compiling Lilypond 1.7.4 Ralph Little wrote: Hi, I am trying to get Lily 1.7.4 up and running on Redhat 8 I have built and installed Guile1.6 from source, and there is a /usr/local/lib/libguile.so.12 (sym linked to libguile.so.12.3.0), and guile (/usr/local/bin/guile) fires up fine. I saw some posts on a similar vein previously, and I have checked that /usr/local/bin is in /etc/ld.so.conf. I think you should rather include /usr/local/lib not bin. After you've checked that you should execute ldconfig as root (which wouldn't hurt anyway). regards Klaus -- Our communications with you matter to us. This e-mail and any attachments are confidential and are sent on the basis of our copyright, e-mail and security policy which can be inspected at our website at http://www.tribaldata.co.uk/html/contact.html#6. If you are not the intended recipient, please notify the sender and delete this message. Thank you. -- ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling Lilypond 1.7.4
Ralph Little wrote: Hi, I am trying to get Lily 1.7.4 up and running on Redhat 8 I have built and installed Guile1.6 from source, and there is a /usr/local/lib/libguile.so.12 (sym linked to libguile.so.12.3.0), and guile (/usr/local/bin/guile) fires up fine. I saw some posts on a similar vein previously, and I have checked that /usr/local/bin is in /etc/ld.so.conf. I think you should rather include /usr/local/lib not bin. After you've checked that you should execute ldconfig as root (which wouldn't hurt anyway). regards Klaus ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
