The x11-misc/xscreensaver-4.09 build fails with the following access violation message, when emerged using Portage 2.0.48_pre6 (default-x86-1.4, gcc-3.2.2, glibc-2.3.2-r1). I'm including the last gcc invocation before the failure, but it appears that the failure only occurs once we're out of that gcc invocation. gcc -Wall -Wstrict-prototypes -Wnested-externs -std=c89 -U__STRICT_ANSI__ -L/usr/lib -o extrusion extrusion.o extrusion-helix2.o extrusion-helix3.o extrusion-helix4.o extrusion-joinoffset.o extrusion-screw.o extrusion-taper.o extrusion-twistoid.o xpm-ximage.o rotator.o trackball.o gltrackball.o screenhack-gl.o xlock-gl.o fps.o ../xlockmore.o ../../utils/resources.o ../.. /utils/visual.o ../../utils/visual-gl.o ../../utils/usleep.o ../.. /utils/yarandom.o ../../utils/hsv.o ../../utils/colors.o -L/usr/X11R6/lib -Wl,--export-dynamic -lgdk_pixbuf_xlib-2.0 -lgdk_pixbuf-2.0 -lm -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lGL -lGLU -lSM -lICE -lXt -lX11 -lXmu -lXext -lm -L/usr/X11R6/lib -lgle -Wl,--export-dynamic -lgdk_pixbuf_xlib-2.0 -lgdk_pixbuf-2.0 -lm -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lGL -lGLU -lSM -lICE -lXt -lX11 -lXmu -lXext -lm make[1]: Leaving directory `/var/tmp/portage/xscreensaver-4. 09/work/xscreensaver-4.09/hacks/glx' --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-xscreensaver-4.09-3169.log" open_wr: /var/lib/rpm/__db.Name. -------------------------------------------------------------------------------- where the referenced log file just contains this open_wr: line. Notably, this ebuild is a rebuild :), i.e. I already have xscreensaver-4.09 successfully emerged with an earlier setup (I believe it was the last stable gcc and glibc, i.e. gcc-3.2.2 and glibc-2.3.1-r4, though I'm not 100% sure on that). After updating gcc and glibc to the ~x86 versions, I attempted to rebuild xscreensaver and got this. Full emerge info output follows. Portage 2.0.48_pre6 (default-x86-1.4, gcc-3.2.2, glibc-2.3.2-r1) ================================================================= System uname: 2.4.20-gentoo-r4 i686 AMD Athlon(tm) XP 2000+ GENTOO_MIRRORS="http://ftp.linux.is/gentoo http://gentoo.oregonstate.edu/ http: //www.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /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/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib directfb gdbm berkdb slang readline arts tetex aalib nas svga ggi tcltk java guile mysql X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl mozilla apache2" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O3 -pipe -fforce-addr -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4" CXXFLAGS="-march=athlon-xp -O3 -pipe -fforce-addr -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
(sorry if this was the wrong component to file this ... is there a more appropriate one, for x11-misc stuff?)
I am getting the exact same ACCESS VIOLATION error while trying to build gphoto2-2.1.0 (it's also trying to access /var/lib/rpm/__db.Name file). Note that I still get the error even if I disabled the sandbox feature.
This problem did not occur in emerging xscreensaver-4.09-r1 ... so isn't this bug fixed?
Hrm...granted it's another package showing the exact bhaviour...so xscreensaver may be off the hoock....but that file seems to be gaining some popularity out of the sandbox ;)
this bug has been fixed a while back with the new xscreensavers. its because the configure script tries to run rpm -q. the violation only occurs when rpm is installed.
