Re: Lilypond 2.6.1 on Gentoo: libstdc++

[Daniel Johnson]

Dear Martin --

I took another look at your error message.  I think that if you scroll
further up in your error messages, you'll find that there was a
non-fatal error in processing a .ly file; this causes problems for
texi2dvi later.  Also, have you explicitly disabled the "doc" USE flag
for this?  I.e. added the following to /etc/portage/package.use:
media-sound/lilypond -doc
You can make sure by using the ask-verbose flag when emerging:
emerge -av lilypond
I could almost swear that somehow the "doc" USE flag is being set. 
Also, if you discover the failed processing of a .ly file, it is almost
assuredly because of a problem with Guile 1.6.7.  If you want to try
updating Guile to the CVS version, you can find instructions here:
http://lists.gnu.org/archive/html/lilypond-user/2005-07/msg00031.html
Just ignore steps 12-18, since the ebuild available from the Gentoo
bugzilla handles that part for you.  You'll find that Lilypond builds
much faster with the CVS Guile.

--Daniel

Martin Brodbeck wrote:

> Daniel Johnson schrieb:
>
>> 1. su to root.
>> 2. Make sure you have PORTDIR_OVERLAY set to /usr/local/portage in
>> /etc/make.conf.
>> 3. mkdir -p /usr/local/portage/app-text/mftrace
>> 4. cp /usr/portage/app-text/mftrace/mftrace-1.1.2.ebuild
>> /usr/local/portage/app-text/mftrace/mftrace-1.1.11.ebuild
>> 5. cd /usr/local/portage/app-text/mftrace/
>> 6. ebuild mftrace-1.1.11.ebuild digest
>> 7. Make sure the following line is in /etc/portage/package.keywords:
>> app-text/mftrace ~x86
>>
>> Now when you emerge lilypond, it should emerge the updated mftrace
>> first.
>
>
> In the meantime I've already tried this but without success.  :(
> mftrace --version gives me 1.1.11 so this is ok. But I still get the
> mentioned lilypond-error...
>
> Doesn't it seem to be a texi2dvi problem (I've got texinfo-4.8
> installed)?
>
> Why does it even try to do something in the Documentation directory
> since I've removed the "doc" USE flag?
>
> Martin