Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 630710 - media-sound/lilypond fails to build -- "Cannot open /var/tmp/portage/media-sound/lilypond-2.19.64/work/lilypond-2.19.64/mf/out/feta13.pfb"
Summary: media-sound/lilypond fails to build -- "Cannot open /var/tmp/portage/media-so...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal major with 1 vote (vote)
Assignee: Tim Harder
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-11 17:52 UTC by Markus Walter
Modified: 2018-01-07 05:40 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build log (bzipped) (lilypond-2.19.64:20170911-082832.log.bz2,204.79 KB, application/x-bzip)
2017-09-11 17:53 UTC, Markus Walter
Details
emerge --info (info.txt,7.82 KB, text/plain)
2017-09-11 17:53 UTC, Markus Walter
Details
t1utils-1.41-memmem.patch (t1utils-1.41-memmem.patch,703 bytes, patch)
2017-12-31 15:28 UTC, Karl Lindén
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Walter 2017-09-11 17:52:30 UTC
On my ~amd64 machine I see the following error when merging lilypond.

Cannot open /var/tmp/portage/media-sound/lilypond-2.19.64/work/lilypond-2.19.64/mf/out/feta13.pfb
The requested file, feta13.pfb, does not exist
MergeFonts: Can't find font: feta13.pfb
Called from...
 emmentaler-13.genpe: line 17
make[1]: *** [GNUmakefile:138: out/emmentaler-13.otf] Error 1
Comment 1 Markus Walter 2017-09-11 17:53:05 UTC
Created attachment 494036 [details]
build log (bzipped)
Comment 2 Markus Walter 2017-09-11 17:53:22 UTC
Created attachment 494038 [details]
emerge --info
Comment 3 Miroslav Šulc gentoo-dev 2017-12-03 15:06:57 UTC
anybody has a solution or workaround for this issue? it seems to affect all available versions.
Comment 4 Jonas Stein gentoo-dev 2017-12-03 19:58:15 UTC
Confirmed by Miroslav
Comment 5 Mike Benson 2017-12-08 01:26:41 UTC
I know this is not a resolution, but I have found the point where things break.

scripts/out/mf2pt1 invokes /usr/bin/t1asm (from app-text/t1utils). 

t1asm crashes with a SEGSEGV(SEGV_MAPERR) whilst writing out the .pt1 file.

I'm running hardened, but I can't see if this is a pax issue.
Comment 6 markus 2017-12-13 09:33:43 UTC
Workaround: 

lilypond-2.19.80 merges fine with current stable t1utils-1.39 (above failure occurs with t1utils-1.41-r1, I've not tried t1utils-1.40 tough).

ty
Comment 7 Markus Walter 2017-12-19 19:37:48 UTC
(In reply to markus from comment #6)
> lilypond-2.19.80 merges fine with current stable t1utils-1.39 (above failure
> occurs with t1utils-1.41-r1, I've not tried t1utils-1.40 tough).

Sadly, this did not work for me.
Comment 8 Karl Lindén 2017-12-31 10:29:04 UTC
(In reply to Markus Oehme from comment #7)
> (In reply to markus from comment #6)
> > lilypond-2.19.80 merges fine with current stable t1utils-1.39 (above failure
> > occurs with t1utils-1.41-r1, I've not tried t1utils-1.40 tough).
> 
> Sadly, this did not work for me.

It works fine for me for versions 2.19.64 and 2.19.80 with the stable t1utils. Do you get the same error?
Comment 9 Karl Lindén 2017-12-31 15:28:27 UTC
Created attachment 512286 [details, diff]
t1utils-1.41-memmem.patch

If I apply this patch (it is merely the current master of kohler/t1utils, which is the t1utils upstream) to app-text/t1utils-1.41 it builds fine.

Could you try this patch and confirm if it works? I will send a PR as soon as I get confirmation that it works.
Comment 10 Markus Walter 2018-01-01 13:44:35 UTC
(In reply to Karl Lindén from comment #8)
> (In reply to Markus Oehme from comment #7)
> > (In reply to markus from comment #6)
> > > lilypond-2.19.80 merges fine with current stable t1utils-1.39 (above failure
> > > occurs with t1utils-1.41-r1, I've not tried t1utils-1.40 tough).
> > 
> > Sadly, this did not work for me.
> 
> It works fine for me for versions 2.19.64 and 2.19.80 with the stable
> t1utils. Do you get the same error?

I actually do have a different error right now -- which is bug #642962 -- so that I'm currently not able to tell whether I had a spurious effect. So your suggestion might be perfectly working and I do not see this.
Comment 11 Larry the Git Cow gentoo-dev 2018-01-07 05:40:58 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dd4f80ff24cc83d1aeabb699c973bf1879d29b81

commit dd4f80ff24cc83d1aeabb699c973bf1879d29b81
Author:     Karl Linden <karl.j.linden@gmail.com>
AuthorDate: 2017-12-31 15:30:18 +0000
Commit:     Alexis Ballier <aballier@gentoo.org>
CommitDate: 2018-01-07 05:40:19 +0000

    app-text/t1utils: apply memmem patch from upstream
    
    Closes: https://bugs.gentoo.org/630710
    Closes: https://bugs.gentoo.org/642586
    Package-Manager: Portage-2.3.19, Repoman-2.3.6

 app-text/t1utils/files/t1utils-1.41-memmem.patch | 27 +++++++++++++++++++++++
 app-text/t1utils/t1utils-1.41-r2.ebuild          | 28 ++++++++++++++++++++++++
 2 files changed, 55 insertions(+)