When I try to emerge -u mrproject, during the libmrproject merge I get: make[1]: Leaving directory `/var/tmp/portage/libmrproject-0.10/work/libmrproject-0.10' --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-libmrproject-0.10-30714.log" unlink: /usr/share/pygtk/2.0/codegen/defsparser.pyc open_wr: /usr/share/pygtk/2.0/codegen/defsparser.pyc unlink: /usr/share/pygtk/2.0/codegen/scmexpr.pyc open_wr: /usr/share/pygtk/2.0/codegen/scmexpr.pyc unlink: /usr/share/pygtk/2.0/codegen/definitions.pyc open_wr: /usr/share/pygtk/2.0/codegen/definitions.pyc unlink: /usr/share/pygtk/2.0/codegen/argtypes.pyc open_wr: /usr/share/pygtk/2.0/codegen/argtypes.pyc unlink: /usr/share/pygtk/2.0/codegen/override.pyc open_wr: /usr/share/pygtk/2.0/codegen/override.pyc Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 18187 [details] libmrproject-0.10 sandbox access violation Confirmed, see complete log in the attachment. emerge info: Portage 2.0.49-r5 (default-x86-1.4, gcc-3.3.1, glibc-2.2.5-r2,2.3.2-r1, 2.6.0-test5-mm2) ================================================================= System uname: 2.6.0-test5-mm2 i686 Intel(R) Pentium(R) 4 CPU 1.80GHz ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -march=pentium3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs sandbox ccache distcc usersandbox fixpackages" GENTOO_MIRRORS="ftp://ftp.uninett.no/pub/linux/Gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mmx mpeg ncurses pdflib png quicktime spell truetype xml2 xmms xv gtkhtml alsa gdbm berkdb slang readline arts tetex bonobo svga tcltk java guile X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl mozilla ldap scanner dvd -zlib canna cdr cjk nls xfs xface gtk2"
Also confirmed: --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-libmrproject-0.10-20730.log" unlink: /usr/share/pygtk/2.0/codegen/defsparser.pyc open_wr: /usr/share/pygtk/2.0/codegen/defsparser.pyc unlink: /usr/share/pygtk/2.0/codegen/scmexpr.pyc open_wr: /usr/share/pygtk/2.0/codegen/scmexpr.pyc unlink: /usr/share/pygtk/2.0/codegen/definitions.pyc open_wr: /usr/share/pygtk/2.0/codegen/definitions.pyc unlink: /usr/share/pygtk/2.0/codegen/argtypes.pyc open_wr: /usr/share/pygtk/2.0/codegen/argtypes.pyc unlink: /usr/share/pygtk/2.0/codegen/override.pyc open_wr: /usr/share/pygtk/2.0/codegen/override.pyc -------------------------------------------------------------------------------- Portage 2.0.49-r5 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r1, 2.6.0-test5-mm1) ================================================================= System uname: 2.6.0-test5-mm1 i686 AMD Duron(tm) Processor ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-tbird -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /etc/env.d /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/init.d /etc/X11/xkb /etc/X11/xdm /etc/X11/xserver /etc/X11/xsm /etc/X11/xinit /etc/env.d /etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-tbird -O2 -pipe -fomit-frame-pointer" DISTDIR="/mnt/test/distfiles" FEATURES="ccache autoaddcvs sandbox distcc prelink" GENTOO_MIRRORS="http://ftp.easynet.nl/mirror/gentoo/ http://ftp.snt.utwente.nl/pub/os/linux/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/mp3/portage" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.nl.gentoo.org/gentoo-portage" USE="x86 oss avi crypt cups encode foomaticdb gif jpeg libg++ mad mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gtkhtml alsa gdbm berkdb slang readline arts tetex aalib nas bonobo svga ggi tcltk java guile ruby mysql postgres X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde opengl mozilla gphoto2 ldap snmp cdr scanner acl acpi apache2 artswrappersuid curl dga dvd flash gd gtk2 imap innodb mbox pda S3TC samba tiff usb wmf xinerama xml -apm -mikmod -motif"
mmm codegen issue.. didn't know libmrproject could use python spider (?) think we need another addwrite (ugleeh..) or lqx can you think of a better solution for this (stopping python from generating optimized binaries) ?
i remember looking at the codegen stuff before, i think we have to patch the codegen program from pygtk to make this all work. right now the addwrite hack is in both gnome-python and pyorbit (iirc). i'll look at this tonight
no, the problem is python itsself generating those optimized sources when they are not available. codegen gets used, python creates optimized binaries and we have a problem. I looked into this a while ago, but couldn't find a way to disable this python behaviour.
Whatever it is, it ceases to be a problem when I run 'SANDBOX_DISABLED=1 emerge --update mrproject' instead. That command compiles without errors in the same environment as described above. Hope I didn't do anything stupid here, but the freshly emerged result from that, MrProject 0.10, does work without showing any weird behaviour...
disable sandbox and you loose all benefits gentoo gives you in package tracking, but its your choice. disable_sandbox is never a proper solution to a problem.
*** Bug 29303 has been marked as a duplicate of this bug. ***
fixed the ebuild the ugly way, should look for a better solution later. added python and postgres USE flags and cleaned up. That should fix these issue at least.
no need to keep this particular bug open for the underlying issue. closing