Compiling Lilypond-2.6.0 On Gentoo

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Compiling Lilypond-2.6.0 On Gentoo

J. Scott Amort
Hi All,

I am eager to give Lilypond-2.6.0 a try!

However, on my Gentoo box, I get the following error during the compile:

mf-nowin -progname=mf "\mode:=laserjet; nonstopmode; input feta11.mf;"
This is METAFONT, Version 2.71828 (Web2C 7.5.4)
kpathsea: Running mktexfmt mf.base
tcfmgr: config file `tcfmgr.map' (usually in $TEXMFMAIN/texconfig) not
found.
fmtutil: config file `fmtutil.cnf' not found.
I can't find the base file `mf.base'!
make[1]: *** [out/feta11.tfm] Error 1
make[1]: Leaving directory
`/home/portage/lilypond-2.6.0/work/lilypond-2.6.0/mf'make: *** [all]
Error 2

I did a bit of searching around, and it seems that there are a few other
gentoo users with a similar error (albeit on an earlier version of
lilypond - 2.5.2: http://bugs.gentoo.org/show_bug.cgi?id=90334 ).  It
seems to be related to tetex, but I do have the latest gentoo version
installed (3.0-r2).

However, I also see that I can do a:

make -C mf get-pfa

that appears to download and extract pretraced fonts from an rpm
package.  Cool.  But, after the above make (apparently successfully), I
follow it up with a 'make all' and still run into the same error as
above.

So, could anyone shed some light on the original error; or perhaps
explain how the 'get-pfa' option should be used.

Thanks very much for you help, and for a great program!

Best,
Scott

--
"Oh, people can come up with statistics to prove anything. 14% of people
know that." -- Homer Simpson



_______________________________________________
lilypond-user mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-user
Reply | Threaded
Open this post in threaded view
|

Re: Compiling Lilypond-2.6.0 On Gentoo

Joe Neeman
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
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-user

lilypond-ebuild.tar.bz2 (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Compiling Lilypond-2.6.0 On Gentoo

J. Scott Amort
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
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-user
Reply | Threaded
Open this post in threaded view
|

Re: Compiling Lilypond-2.6.0 On Gentoo

Daniel Johnson-2
In reply to this post by Joe Neeman
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
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-user
Reply | Threaded
Open this post in threaded view
|

Re: Compiling Lilypond-2.6.0 On Gentoo

J. Scott Amort
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
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-user