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

[Han-Wen Nienhuys]

2007/4/20, Marijn Schouten (hkBst) <address@hidden>:
> 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,

Hi,

here is a hint for a real solution: the scripts that are in
$(top-build-dir)/$(outdir)/bin/ should
import modules from  $(top-build-dir)/$(outdir)/share/ .   Can you see
what happens if you hack scripts/GNUmakefile to call the scripts
through the symlinks in    $(top-build-dir)/$(outdir)/bin/ ?


--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen