lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Gentoo sandbox violations [was Re: sys.path.insert]


From: Marijn Schouten (hkBst)
Subject: Gentoo sandbox violations [was Re: sys.path.insert]
Date: Fri, 20 Apr 2007 17:03:48 +0200
User-agent: Thunderbird 2.0.0.0 (X11/20070419)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marijn Schouten (hkBst) wrote:
> Han-Wen Nienhuys wrote:
>> Marijn Schouten (hkBst) escreveu:
>>>> This should be fixed in current GIT.
>>> I'm getting the same errors in 2.10.17,
>>>
>> hoi, kan je voor me checken of 2.11.18  dezelfde problemen heeft? 
> 
> 2.10.20 still has the same problem if 2.10.20 is already installed.
> 
> 2.11.20 failed to compile when I compiled it with docs, but it compiled fine 
> without docs. After it
> was installed without docs, I could build it with docs but I got the same 
> sandbox violations:
> 
> unlink:    /usr/share/lilypond/2.11.20/python/lilylib.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/lilylib.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/convertrules.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/convertrules.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/lilylib.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/lilylib.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/convertrules.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/convertrules.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/lilylib.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/lilylib.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/fontextract.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/fontextract.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/lilylib.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/lilylib.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/fontextract.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/fontextract.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/lilylib.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/lilylib.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/lilylib.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/lilylib.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/lilylib.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/lilylib.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/lilylib.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/lilylib.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/lilylib.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/lilylib.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/lilylib.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/lilylib.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/lilylib.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/lilylib.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/musicxml.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/musicxml.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/rational.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/rational.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/musicexp.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/musicexp.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/lilylib.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/lilylib.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/musicxml.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/musicxml.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/rational.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/rational.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/musicexp.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/musicexp.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/fontextract.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/fontextract.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/fontextract.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/fontextract.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/fontextract.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/fontextract.pyc
> unlink:    /usr/share/lilypond/2.11.20/python/fontextract.pyc
> open_wr:   /usr/share/lilypond/2.11.20/python/fontextract.pyc
> 
> Marijn

Using 2.11.22 for testing now. Most of the problems are caused by a single
line. Using the patch

- --- stepmake/stepmake/help2man-rules.make.old   2007-04-20 14:16:42.000000000
+0200
+++ stepmake/stepmake/help2man-rules.make       2007-04-20 14:17:21.000000000
+0200
@@ -19,7 +19,7 @@

 ifeq ($(strip $(CROSS)),no)
 $(outdir)/%.1: $(outdir)/%
- -       $(HELP2MAN_COMMAND)
+       echo nothing
 else
 # When cross building, some manpages will not build because the
 # executable does not run.  We assume the manpages to be generated

to turn off that line leaves only the fontextract.pyc problem. Another way to
do it is by using the workaround

# help2man runs scripts directly, so they need to be able to find modules
# in build directory (otherwise they look in ${ROOT} and violate sandbox)
for dir in scripts/{share,lib}/lilypond/current; do
        mkdir -p ${dir}
        ln -s ${S}/python ${dir}/python
done

in the build script, which creates symlinks to places in the source directory
(S), where it is ok to write.
There seem to be pyc files in ${S}/python/out/ which probably should be used
instead.

Hoping for a real solution,

Marijn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGKNZUp/VmCx0OL2wRArc2AKCJpZYal4/RGU6EOdUgaSIhPscUNwCgyK5K
0pF0azAhiCJJLVqecvp6jlk=
=J7U1
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]