Re: lilypond on freebsd 6.1
Karl Hammar karl at aspodata.se writes: After installing lilypond 2.10.5 freebsd-x86 I get this, /usr/libexec/ld-elf.so.1 :shared object lidm.so.2 not found required by lilypond. Are you sure it said lidm and not libm? What can I do next to get it working? I would try ldd, like: $ ldd /usr/bin/lilypond libdl.so.2 = /lib/libdl.so.2 (0x4003) libpangoft2-1.0.so.0 = /usr/lib/libpangoft2-1.0.so.0 (0x40034000) ... And resolve any not found lines, which will probably be libm. Do you have (this is BSD4.11): $ ls -l /usr/lib/libm.s* lrwxrwxrwx 1 root wheel 9 Sep 15 2005 /usr/lib/libm.so - libm.so.2 -r--r--r-- 1 root wheel 117024 Jan 21 2005 /usr/lib/libm.so.2 Regards, /Karl --- Karl HammarAspö Data karl at aspodata.se Lilla Aspö 2340Networks S-742 94 Östhammar +46 173 140 57 Computers Sweden +46 70 511 97 84 Consulting --- On my laptop I did a new install of freebsd 6.1 One of the first things is trying to get lilypond op and running. This is the result : .!!! marcel# ldd /usr/local/lilypond/usr/bin/lilypond /usr/local/lilypond/usr/bin/lilypond: libintl.so.8 = not found (0x0) libguile.so.17 = not found (0x0) libgmp.so.7 = not found (0x0) libpangoft2-1.0.so.1400 = not found (0x0) libpango-1.0.so.1400 = not found (0x0) libgobject-2.0.so.1000 = not found (0x0) libgmodule-2.0.so.1000 = not found (0x0) libglib-2.0.so.1000 = not found (0x0) libiconv.so.6 = not found (0x0) libfontconfig.so.2 = not found (0x0) libfreetype.so.9 = /usr/local/lib/libfreetype.so.9 (0x2832c000) libz.so = /usr/lib/libz.so (0x28391000) libm.so.2 = not found (0x0) libc.so.4 = not found (0x0) And the ls -l : marcel# ls -l /usr/lib/libm.s* lrwxrwxrwx 1 root wheel 14 Dec 25 17:09 /usr/lib/libm.so - /lib/libm.so.4 lrwxr-xr-x 1 root wheel 9 Dec 27 09:07 /usr/lib/libm.so.2 - libm.so.3 What I don't understand is how to solve this missing libm. because it is there in /usr/lib directory. When I do lilypond it come back with this message; marcel# lilypond /usr/libexec/ld-elf.so.1: Shared object libm.so.2 not found, required by lilypond Regards Marcel. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond on freebsd 6.1
Thank you very much. Did as you wrote and it works perfectley. regards Marcel. 2006/12/27, Kim Shrier [EMAIL PROTECTED]: On Dec 27, 2006, at 8:51 AM, Marcel Campenhout wrote: After installing lilypond 2.10.5 freebsd-x86 I get this, /usr/libexec/ld-elf.so.1 :shared object lidm.so.2 not found required by lilypond. I made a sym.link from de libm.so.3 -- libm.so.2. placed one in /usr/lib and one in /usr/libexec but the result is the same error. What can I do next to get it working? regards Marcel. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user Just symlinking libm.so.2 to libm.so.3 or making a copy of libm.so.3 and renaming it to libm.so.2 will not work since the library has version information in it and the dynamic library loader will not be faked out. libm.so.2 is from FreeBSD 4.x so you need to install the compat4x port. This is located in /usr/ports/misc/compat4x. After making and installing this port, lilypond should be able to locate the libm.so.2 library. If you don't want to build the port, there is a binary package version that can be installed by retrieving the package from the FreeBSD ftp site or it should be on your 6.1 installation CD's. Kim -- Kim Shrier - principal, Shrier and Deihl - mailto:[EMAIL PROTECTED] Remote Unix Network Admin, Security, Internet Software Development Tinker Internet Services - Superior FreeBSD-based Web Hosting http://www.tinker.com/ ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond and FreeBSD
On 17-Jun-05, at 12:45 PM, Basil Crow wrote: Assuming that I have user (not root) access to a FreeBSD system with compilers, etc., could I get LilyPond running? I could contact the box's maintainer and ask for the dependencies to be installed in order for me to be able to compile LilyPond into my home directory. But what are LilyPond's current dependencies for FreeBSD, and is it possible to compile it into one's home directory in this way? Yes, absolutely. Specify the target dir with ./autogen.sh --prefix=$HOME/usr (assuming that's where you want to install it). As for dependencies, see the INSTALL docs. (I know they can all be satisfied in freebsd, since I installed lilypond on freebsd recently, but I can't remember everything I installed) Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond on FreeBSD
Gordon Gilbert writes: The latest version for ports is stil 2.2.2. Any ideas on when the newer version might be built and put in ports? The LilyPond download page lists Patrick Atamaniuk as FreeBSD maintainer. You may want to contact him about this. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond on FreeBSD.
I have tetex 2.01.
This sort of strangness makes me suspicious. Only I would never
know unless you told me.
I deinstalled tetex, recompiled and installed it.
I ran texconfig with better, but still awful results afterward.
My dvi file would come up but the notes looked like stems with
2 small detached dots.
I recompiled and reinstalled lilypond.
I also changed the quoting in lilypond-profile back to it's original state.
Now it looks like it's working. Better even than 1.6.12 which
couldn't do anything but quarter notes.
The resolution looks bad though. 32nd note bars are run together. It's tolerable
at 25%. and pretty good at 50%.
The postscript looses the bars and the lines above and below the staff. I'm not
sure what to do about that either. I haven't read up on the ps doc. I must not
have something installed or set up.
xdvi gave me this the first time. Is there a better mode that I should
be using. I didn't have a clue, what to tell texconfig...
xdvi foo.dvi
kpathsea: Running mktexpk --mfmode agfafzz --bdpi 406 --mag 1+0/406 --dpi 406 feta20
mktexpk: Running mf-nowin -progname=mf \mode:=agfafzz; mag:=1+0/406; nonstopmode;
input feta20
This is METAFONT, Version 2.7182 (Web2C 7.4.5)
(/usr/local/share/lilypond/1.8.0/fonts/source/feta20.mf
(/usr/local/share/lilypond/1.8.0/fonts/source/feta-autometric.mf
**
Using feta Autometric macros.
Do not worry about the @ signs in the output, they are not errors.
thanks,
Eric
- Mats Bengtsson's Original Message -
Eric Gebhart wrote:
Here's more debug. It still doesn't make any sense. There is a missing }
- Mats Bengtsson's Original Message -
As I said before, please, please keep the discussion on the mailing
list, don't just reply to me in private.
Sure. If you'll do the same. It would be a lot easier to keep it on
the list if you didn't keep responding to me privately.
Some people get very upset if you forward a privately sent email
to a mailing list. I respect such an opinion and send private
answers to those sending me a question in private email. At the
same time, I keep urging them to followup to the email list and
tell them that they are welcome to quote my text.
You may want to set the environment variable KPATHSEA_DEBUG to -1
and then run xdvi again. You will get tons of debugging information
on stdout that might give you a clue.
Some comments below. I think your teTeX setup looks a bit strange.
The file where all these settings are done for teTeX can be found using
kpsewhich texmf.cnf. Do you know what teTeX version you have installed?
Can you find out what changes have been introduced in the FreeBSD
package compared to standard teTeX (and why)?
I don't recommend to start playing around with the texmf.cnf file if you
don't know exactly what you are doing. Rather, I would start with a
fresh copy of the file from the standard teTeX source code distribution
which can be found at any mirror of www.ctan.org. Make sure to find a
copy corresponding to your installed version.
Here's part of what it says. That mismatched { has got to be the problem.
Eric
...
kdebug:hash_lookup(PKFONTS) =
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
This looks strange! In both teTeX 1.07 and teTeX 2.02, the variable is
set to
.:{$TEXMF/fonts,$VARTEXFONTS}/pk/{$MAKETEX_MODE,modeless}//
...
kdebug:hash_lookup(VARTEXFONTS) = /var/tmp/texfonts /var/tmp/texfonts
This also looks strange! First of all the same path is duplicated,
secondly if you had several paths they shouldnt be separated by a space.
/Mats
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond on FreeBSD.
It seems that your xdvi is setup to use fairly low resolution fonts,
(406 dpi). Either you could use 'texconfig mode' to change the setup
to ljfour or some other 600dpi mode. If you want the agfafzz mode
for your printer but still want higher resolution in xdvi, change
manually in the file .../texmf/xdvi/Xdvi setting the mfmode to ljfour
and the pixelsPerInch to 600.
/Mats
Eric Gebhart wrote:
I have tetex 2.01.
This sort of strangness makes me suspicious. Only I would never
know unless you told me.
I deinstalled tetex, recompiled and installed it.
I ran texconfig with better, but still awful results afterward.
My dvi file would come up but the notes looked like stems with
2 small detached dots.
I recompiled and reinstalled lilypond.
I also changed the quoting in lilypond-profile back to it's original state.
Now it looks like it's working. Better even than 1.6.12 which
couldn't do anything but quarter notes.
The resolution looks bad though. 32nd note bars are run together. It's tolerable
at 25%. and pretty good at 50%.
The postscript looses the bars and the lines above and below the staff. I'm not
sure what to do about that either. I haven't read up on the ps doc. I must not
have something installed or set up.
xdvi gave me this the first time. Is there a better mode that I should
be using. I didn't have a clue, what to tell texconfig...
xdvi foo.dvi
kpathsea: Running mktexpk --mfmode agfafzz --bdpi 406 --mag 1+0/406 --dpi 406 feta20
mktexpk: Running mf-nowin -progname=mf \mode:=agfafzz; mag:=1+0/406; nonstopmode;
input feta20
This is METAFONT, Version 2.7182 (Web2C 7.4.5)
(/usr/local/share/lilypond/1.8.0/fonts/source/feta20.mf
(/usr/local/share/lilypond/1.8.0/fonts/source/feta-autometric.mf
**
Using feta Autometric macros.
Do not worry about the @ signs in the output, they are not errors.
thanks,
Eric
- Mats Bengtsson's Original Message -
Eric Gebhart wrote:
Here's more debug. It still doesn't make any sense. There is a missing }
- Mats Bengtsson's Original Message -
As I said before, please, please keep the discussion on the mailing
list, don't just reply to me in private.
Sure. If you'll do the same. It would be a lot easier to keep it on
the list if you didn't keep responding to me privately.
Some people get very upset if you forward a privately sent email
to a mailing list. I respect such an opinion and send private
answers to those sending me a question in private email. At the
same time, I keep urging them to followup to the email list and
tell them that they are welcome to quote my text.
You may want to set the environment variable KPATHSEA_DEBUG to -1
and then run xdvi again. You will get tons of debugging information
on stdout that might give you a clue.
Some comments below. I think your teTeX setup looks a bit strange.
The file where all these settings are done for teTeX can be found using
kpsewhich texmf.cnf. Do you know what teTeX version you have installed?
Can you find out what changes have been introduced in the FreeBSD
package compared to standard teTeX (and why)?
I don't recommend to start playing around with the texmf.cnf file if you
don't know exactly what you are doing. Rather, I would start with a
fresh copy of the file from the standard teTeX source code distribution
which can be found at any mirror of www.ctan.org. Make sure to find a
copy corresponding to your installed version.
Here's part of what it says. That mismatched { has got to be the problem.
Eric
...
kdebug:hash_lookup(PKFONTS) =
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
This looks strange! In both teTeX 1.07 and teTeX 2.02, the variable is
set to
.:{$TEXMF/fonts,$VARTEXFONTS}/pk/{$MAKETEX_MODE,modeless}//
...
kdebug:hash_lookup(VARTEXFONTS) = /var/tmp/texfonts /var/tmp/texfonts
This also looks strange! First of all the same path is duplicated,
secondly if you had several paths they shouldnt be separated by a space.
/Mats
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
--
=
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://mail.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond on FreeBSD.
I changed the lilypond-profile and now it seems to be getting further.
I changed This:
TEXMF={$datadir,`kpsexpand \\$TEXMF`}
To this:
TEXMF={ $datadir,`kpsexpand \\$TEXMF`}
The extra { is now gone.
Now it can't find mf.base. It looks like it knows where it is,
but it refuses to look there.
locate mf.base
/usr/local/share/texmf/web2c/mf.base
This is part of the log.
kdebug: = /home/eric/music:/usr/local/share/lilypond/1.8.0/web2c:/web2c
kdebug: before expansion = .:$TEXMF/web2c
kdebug: application override path = (none)
kdebug: application config file path = (none)
kdebug: texmf.cnf path = .:$TEXMF/web2c
kdebug: compile-time path = .:/usr/local/share/texmf/web2c
kdebug: default suffixes = .base
kdebug: other suffixes = (none)
kdebug: search only with suffix = 0
kdebug: numeric format value = 5
kdebug: runtime generation program = (none)
kdebug: extra program args = (none)
kdebug: program enabled = 0
kdebug: program enable level = 0
kdebug:start search(file=mf.base, must_exist=0, find_all=0,
path=/home/eric/music:/usr/local/share/lilypond/1.8.0/web2c:/web2c).
kdebug:path element /usr/local/share/lilypond/1.8.0/web2c =
kdebug:path element /web2c =
kdebug:search(mf.base) =
kdebug:start search(file=mf.base, must_exist=1, find_all=0,
path=/home/eric/music:/usr/local/share/lilypond/1.8.0/web2c:/web2c).
kdebug:search(mf.base) =
I can't find the base file `mf.base'!
Eric
- Eric Gebhart's Original Message -
Here's more debug. It still doesn't make any sense. There is a missing }
- Mats Bengtsson's Original Message -
As I said before, please, please keep the discussion on the mailing
list, don't just reply to me in private.
Sure. If you'll do the same. It would be a lot easier to keep it on
the list if you didn't keep responding to me privately.
You may want to set the environment variable KPATHSEA_DEBUG to -1
and then run xdvi again. You will get tons of debugging information
on stdout that might give you a clue.
Here's part of what it says. That mismatched { has got to be the problem.
Eric
kdebug: program enable level = 0
kdebug:start search(file=feta20.vf, must_exist=0, find_all=0,
path=.:/usr/local/share/lilypond/1.8.0/fonts//vf//:/usr/local/share/texmf/fonts//vf//).
kdebug:hash_lookup(/usr/local/share/lilypond/1.8.0/fonts/source) = (nil)
kdebug:dir_links(/usr/local/share/lilypond/1.8.0/fonts/source) = 2
kdebug:hash_lookup(/usr/local/share/lilypond/1.8.0/fonts/afm) = (nil)
kdebug:dir_links(/usr/local/share/lilypond/1.8.0/fonts/afm) = 2
kdebug:hash_lookup(/usr/local/share/lilypond/1.8.0/fonts/tfm) = (nil)
kdebug:dir_links(/usr/local/share/lilypond/1.8.0/fonts/tfm) = 2
kdebug:path element /usr/local/share/lilypond/1.8.0/fonts//vf// =
kdebug:hash_lookup(feta20.vf) = (nil)
kdebug:hash_lookup(feta20.vf) = (nil)
kdebug:search(feta20.vf) =
kdebug:hash_lookup(MAKETEXPK.xdvi) = (nil)
kdebug:hash_lookup(MAKETEXPK) = (nil)
kdebug:hash_lookup(PKFONTS.xdvi) = (nil)
kdebug:hash_lookup(PKFONTS) =
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
kdebug:hash_lookup(VARTEXFONTS.xdvi) = (nil)
kdebug:hash_lookup(VARTEXFONTS) = /var/tmp/texfonts /var/tmp/texfonts
warning: {{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts: Unmatched
{.
warning: /var/tmp/texfonts}//pk/{/: Unmatched {.
kdebug:Search path for pk files (from texmf.cnf)
kdebug: =
.:{{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts:/var/tmp/texfonts}//pk/{/:modeless}//
kdebug: before expansion =
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
kdebug: application override path = (none)
kdebug: application config file path = (none)
kdebug: texmf.cnf path =
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
kdebug: compile-time path =
.:{/usr/local/share/texmf/fonts,/var/tex/fonts}//pk/$MAKETEX_MODE//
kdebug: default suffix = pk
kdebug: other suffixes = (none)
kdebug: search only with suffix = 1
kdebug: numeric format value = 1
kdebug: runtime generation program = MakeTeXPK
kdebug: extra program args = $KPATHSEA_DPI $MAKETEX_BASE_DPI $MAKETEX_MAG
$MAKETEX_MODE
kdebug: program enabled = 0
kdebug: program enable level = 0
kdebug:start search(file=feta20.600pk, must_exist=0, find_all=0,
path=.:{{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts:/var/tmp/texfonts}//pk/{/:modeless}//).
kdebug:path element {{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts
=
kdebug:path element /var/tmp/texfonts}//pk/{/ =
kdebug:path element modeless}// =
kdebug:search(feta20.600pk) =
kdebug:start search(file=dpi600/feta20.pk, must_exist=0, find_all=0,
path=.:{{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts:/var/tmp/texfonts}//pk/{/:modeless}//).
kdebug:search(dpi600/feta20.pk) =
kdebug:start search(file=feta20.600pk, must_exist=1, find_all=0,
Re: lilypond on FreeBSD.
Eric Gebhart wrote:
Here's more debug. It still doesn't make any sense. There is a missing }
- Mats Bengtsson's Original Message -
As I said before, please, please keep the discussion on the mailing
list, don't just reply to me in private.
Sure. If you'll do the same. It would be a lot easier to keep it on
the list if you didn't keep responding to me privately.
Some people get very upset if you forward a privately sent email
to a mailing list. I respect such an opinion and send private
answers to those sending me a question in private email. At the
same time, I keep urging them to followup to the email list and
tell them that they are welcome to quote my text.
You may want to set the environment variable KPATHSEA_DEBUG to -1
and then run xdvi again. You will get tons of debugging information
on stdout that might give you a clue.
Some comments below. I think your teTeX setup looks a bit strange.
The file where all these settings are done for teTeX can be found using
kpsewhich texmf.cnf. Do you know what teTeX version you have installed?
Can you find out what changes have been introduced in the FreeBSD
package compared to standard teTeX (and why)?
I don't recommend to start playing around with the texmf.cnf file if you
don't know exactly what you are doing. Rather, I would start with a
fresh copy of the file from the standard teTeX source code distribution
which can be found at any mirror of www.ctan.org. Make sure to find a
copy corresponding to your installed version.
Here's part of what it says. That mismatched { has got to be the problem.
Eric
...
kdebug:hash_lookup(PKFONTS) =
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
This looks strange! In both teTeX 1.07 and teTeX 2.02, the variable is
set to
.:{$TEXMF/fonts,$VARTEXFONTS}/pk/{$MAKETEX_MODE,modeless}//
...
kdebug:hash_lookup(VARTEXFONTS) = /var/tmp/texfonts /var/tmp/texfonts
This also looks strange! First of all the same path is duplicated,
secondly if you had several paths they shouldnt be separated by a space.
/Mats
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond on FreeBSD.
Here's more debug. It still doesn't make any sense. There is a missing }
- Mats Bengtsson's Original Message -
As I said before, please, please keep the discussion on the mailing
list, don't just reply to me in private.
Sure. If you'll do the same. It would be a lot easier to keep it on
the list if you didn't keep responding to me privately.
You may want to set the environment variable KPATHSEA_DEBUG to -1
and then run xdvi again. You will get tons of debugging information
on stdout that might give you a clue.
Here's part of what it says. That mismatched { has got to be the problem.
Eric
kdebug: program enable level = 0
kdebug:start search(file=feta20.vf, must_exist=0, find_all=0,
path=.:/usr/local/share/lilypond/1.8.0/fonts//vf//:/usr/local/share/texmf/fonts//vf//).
kdebug:hash_lookup(/usr/local/share/lilypond/1.8.0/fonts/source) = (nil)
kdebug:dir_links(/usr/local/share/lilypond/1.8.0/fonts/source) = 2
kdebug:hash_lookup(/usr/local/share/lilypond/1.8.0/fonts/afm) = (nil)
kdebug:dir_links(/usr/local/share/lilypond/1.8.0/fonts/afm) = 2
kdebug:hash_lookup(/usr/local/share/lilypond/1.8.0/fonts/tfm) = (nil)
kdebug:dir_links(/usr/local/share/lilypond/1.8.0/fonts/tfm) = 2
kdebug:path element /usr/local/share/lilypond/1.8.0/fonts//vf// =
kdebug:hash_lookup(feta20.vf) = (nil)
kdebug:hash_lookup(feta20.vf) = (nil)
kdebug:search(feta20.vf) =
kdebug:hash_lookup(MAKETEXPK.xdvi) = (nil)
kdebug:hash_lookup(MAKETEXPK) = (nil)
kdebug:hash_lookup(PKFONTS.xdvi) = (nil)
kdebug:hash_lookup(PKFONTS) =
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
kdebug:hash_lookup(VARTEXFONTS.xdvi) = (nil)
kdebug:hash_lookup(VARTEXFONTS) = /var/tmp/texfonts /var/tmp/texfonts
warning: {{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts: Unmatched {.
warning: /var/tmp/texfonts}//pk/{/: Unmatched {.
kdebug:Search path for pk files (from texmf.cnf)
kdebug: =
.:{{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts:/var/tmp/texfonts}//pk/{/:modeless}//
kdebug: before expansion =
.:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
kdebug: application override path = (none)
kdebug: application config file path = (none)
kdebug: texmf.cnf path = .:{$TEXMF/fonts:$VARTEXFONTS}//pk/{$MAKETEX_MODE:modeless}//
kdebug: compile-time path =
.:{/usr/local/share/texmf/fonts,/var/tex/fonts}//pk/$MAKETEX_MODE//
kdebug: default suffix = pk
kdebug: other suffixes = (none)
kdebug: search only with suffix = 1
kdebug: numeric format value = 1
kdebug: runtime generation program = MakeTeXPK
kdebug: extra program args = $KPATHSEA_DPI $MAKETEX_BASE_DPI $MAKETEX_MAG
$MAKETEX_MODE
kdebug: program enabled = 0
kdebug: program enable level = 0
kdebug:start search(file=feta20.600pk, must_exist=0, find_all=0,
path=.:{{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts:/var/tmp/texfonts}//pk/{/:modeless}//).
kdebug:path element {{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts =
kdebug:path element /var/tmp/texfonts}//pk/{/ =
kdebug:path element modeless}// =
kdebug:search(feta20.600pk) =
kdebug:start search(file=dpi600/feta20.pk, must_exist=0, find_all=0,
path=.:{{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts:/var/tmp/texfonts}//pk/{/:modeless}//).
kdebug:search(dpi600/feta20.pk) =
kdebug:start search(file=feta20.600pk, must_exist=1, find_all=0,
path=.:{{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts:/var/tmp/texfonts}//pk/{/:modeless}//).
kdebug:search(feta20.600pk) =
kdebug:start search(file=dpi600/feta20.pk, must_exist=1, find_all=0,
path=.:{{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts:/var/tmp/texfonts}//pk/{/:modeless}//).
kdebug:search(dpi600/feta20.pk) =
kdebug:hash_lookup(GFFONTS.xdvi) = (nil)
kdebug:hash_lookup(GFFONTS) = .:$TEXMF/fonts//gf/$MAKETEX_MODE//
.:$TEXMF/fonts//gf/$MAKETEX_MODE//
kdebug:Search path for gf files (from texmf.cnf)
kdebug: =
.:/usr/local/share/lilypond/1.8.0/fonts//gf:/usr/local/share/texmf/fonts//gf
kdebug: before expansion = .:$TEXMF/fonts//gf/$MAKETEX_MODE//
kdebug: application override path = (none)
kdebug: application config file path = (none)
kdebug: texmf.cnf path = .:$TEXMF/fonts//gf/$MAKETEX_MODE//
kdebug: compile-time path = .:/usr/local/share/texmf/fonts//gf/$MAKETEX_MODE//
kdebug: default suffix = gf
kdebug: other suffixes = (none)
kdebug: search only with suffix = 1
kdebug: numeric format value = 0
/Mats
Eric Gebhart wrote:
Sorry, I got real busy with work...
kpsexpand \$PKFONTS
.:{{/usr/local/share/lilypond/1.8.0,/usr/local/share/texmf}/fonts:/var/tmp/texfonts}//pk/{/:modeless}//
All the curly's match. I'm really at a loss as to what this could be.
It's very frustrating. Fonts are something I don't know much about.
Eric
- Mats Bengtsson's Original Message -
Please keep the discussion on the mailing list, for the
benefit of yourself
