Bug 82928 – lilypond-2.0.3 emerge fails install with sandbox violation

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Ooblick 2005-02-22 02:53:59 UTC]

I am trying to emerge lilypond - the stable version is 2.0.3. It compiles successfully, but aborts with an ACCESS VIOLATION SUMMARY when trying to install it. The error message includes

 mkdir:     /root/.PfaEdit

Which is causing the failure - this is outside of my build directory which is /var/tmp/portage.

Reproducible: Always
Steps to Reproduce:
1. emerge lilypond

Actual Results:  
make[3]: Leaving directory
`/var/tmp/portage/lilypond-2.0.3/work/lilypond-2.0.3/input/mutopia/R.Schumann'
make[2]: Leaving directory
`/var/tmp/portage/lilypond-2.0.3/work/lilypond-2.0.3/input/mutopia'
make[1]: Leaving directory
`/var/tmp/portage/lilypond-2.0.3/work/lilypond-2.0.3/input'
--------------------------- ACCESS VIOLATION SUMMARY
---------------------------LOG FILE =
"/tmp/sandbox-media-sound_-_lilypond-2.0.3-17886.log"

mkdir:     /root/.PfaEdit
mkdir:     /root/.PfaEdit

[repeated many times]
mkdir:     /root/.PfaEdit
mkdir:     /root/.PfaEdit
--------------------------------------------------------------------------------spiceweasel




Expected Results:  
lilypond should have been emerged.

emerge info:

Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.3.5,
glibc-2.3.4.20040808-r1, 2.6.10-gentoo-r6 i686)
=================================================================
System uname: 2.6.10-gentoo-r6 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 10 2005, 09:14:03)]
dev-lang/python:     2.3.4-r1
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r1
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r1, 2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium4 -fomit-frame-pointer -O3 -pipe -ftracer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium4 -fomit-frame-pointer -O3 -pipe -ftracer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://www.mirrorservice.org/mirror/www.ibiblio.org/
http://ftp.uni-erlangen.de/pub/mirrors/gentoo http://ftp.heanet.ie/pub/gentoo/
http://ftp.easynet.nl/mirror/gentoo/ http://mir.zyrianes.net/gentoo/"
LANG="en_GB"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://gentoo.messagelabs.net/gentoo-portage"
USE="x86 X aalib alsa apache2 apm avi bash-completion berkdb bitmap-fonts bonobo
cdr crypt cups curl dbus eds emboss encode esd f77 faad fam flac font-server
foomatic foomaticdb fortran gcj gdbm gif gimpprint ginac gnome gnutls gpm
gstreamer gtk gtk2 gtkhtml guile hal imagemagick imlib java jpeg junit kerberos
ldap libcaca libg++ libwww mad mikmod mmx mmx2 motif mozilla mpeg mule ncurses
nls nptl objc oggvorbis opengl oss pam pdflib perl plotutils png postgres python
qhull quicktime readline samba sdl slang spell sqlite sse sse2 ssl svga tcltk
tcpd tetex tiff truetype truetype-fonts type1-fonts winbind wmf xml xml2 xmms xv
zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LC_ALL, LDFLAGS

[Comment 1 Ooblick 2005-02-22 04:48:41 UTC]

*** Bug 82945 has been marked as a duplicate of this bug. ***

[Comment 2 Aron Griffis (RETIRED) 2005-02-22 14:48:02 UTC]

Can somebody from the fonts team provide insight here?  I think this error is coming from fontforge.  Is there a better way to workaround this problem than addwrite?

[Comment 3 Mamoru KOMACHI (RETIRED) 2005-03-28 02:14:00 UTC]

Yes, this message is from fontforge.
I don't think there's a better way, though :-/

[Comment 4 Ooblick 2005-08-23 03:25:11 UTC]

Closing this bug as #97574 is the fix and the way forward.