35307 2003-12-07 21:26 0000 fam-2.7.0 fails to compile 2003-12-09 14:04:02 0000 1 1 1 Unclassified Gentoo Linux Applications unspecified x86 Linux RESOLVED FIXED P2 major --- 1 mystilleef@gmail.com foser@gentoo.org marc-gentoo@chabrols.org spider@gentoo.org mystilleef@gmail.com 2003-12-07 21:26:09 0000 fam-2.7.0 fails to compile. Excerps of the error is provided below. ..... ..... ..... configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating include/Makefile config.status: creating lib/Makefile config.status: creating conf/Makefile config.status: creating man/Makefile config.status: creating test/Makefile config.status: creating config.h config.status: executing depfiles commands autom4te-2.58: cannot open configure: Permission denied make: *** [configure] Error 1 !!! ERROR: app-admin/fam-2.7.0 failed. !!! Function src_compile, Line 391, Exitcode 2 !!! emake failed Reproducible: Always Steps to Reproduce: 1. emerge sync 2. emerge -pvuD world 3. emerge -vuD world Actual Results: The fam package appears as one of the software packages on my system that needs to be upgraded. Unfortunately, fam fails to compile. Expected Results: I expected fam to compile and function successfully. Portage 2.0.49-r18 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.0-test11) ================================================================= System uname: 2.6.0-test11 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.4.3.12 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-w -pipe -fforce-addr -fomit-frame-pointer -march=athlon -Os -s" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /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/env.d" CXXFLAGS="-w -pipe -fforce-addr -fomit-frame-pointer -march=athlon -Os -s" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs cvs digest fixpackages sandbox userpriv usersandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j1 -s" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="3dnow X aalib alsa apm avi berkdb cdr crypt cups encode esd foomaticdb gdbm ggi gif gnome gpm gtk gtk2 guile imlib java jpeg libg++ libwww mad mikmod mmx mozilla mpeg nas ncurses nptl oggvorbis opengl oss pam pdflib perl pic png python quicktime readline sdl slang spell ssl svga tcpd tetex truetype vanilla x86 xml2 xv zlib" k@191a.net 2003-12-08 02:57:44 0000 Error confirmed foser@gentoo.org 2003-12-08 03:32:18 0000 Aniruddha what is your emerge info ? can anyone of you attach a config.log ? foser@gentoo.org 2003-12-08 05:39:28 0000 *** Bug 35331 has been marked as a duplicate of this bug. *** foser@gentoo.org 2003-12-08 05:49:31 0000 but spider are you using 'user*' features ? try without them. spider@gentoo.org 2003-12-08 06:46:53 0000 whoo, bugzilla lives. without userpriv and usersandbox it works. permissions thing? mikko.tiihonen@iki.fi 2003-12-08 06:50:39 0000 For some reason the configure script is not writable after the configure: -r-xr-xr-x 1 portage portage 347684 Nov 26 21:47 configure The missing script seems to try to touch it and fails. Suspending the fam ebuild while the configure is running and setting running chmod u+w configure allows the build to continue. Maybe this only fails for people that use sandbox+userprib+usersandbox ? foser@gentoo.org 2003-12-08 07:51:54 0000 yes i assumed that was the problem from the initial error. ok added a chmod fix for the user* users. please rsync in a little while and test. thnx for the report & help mystilleef@gmail.com 2003-12-08 12:28:09 0000 Works now. Thanks for your help and effort. :-) marc-gentoo@chabrols.org 2003-12-09 14:04:02 0000 *** Bug 35386 has been marked as a duplicate of this bug. ***