When I try to emerge libxml2 it goes into an /endless/ loop, that is it fails after an hour or so with a "too many files open" error, while doing configure. I also tried emerging libxml2-2.5.7 but it gives the same result. I discovered it while trying to emerge gnome, when it came to libxml2 it died. It's a problem, cause many programs require libxml2, and I'm therfore unable to get my system working while this bug exists. I've tried to get around it, but haven't succesed. If you need any other information, just say so. Reproducible: Always Steps to Reproduce: 1. Install a new system (1.4 RC4) 2. run: emerge libxml2 Actual Results: #emerge libxml2 <snip> config.status: creating include/libxml/xmlversion.h config.status: creating xml2-config config.status: creating libxml-2.0.pc config.status: creating xml2Conf.sh config.status: creating python/setup.py config.status: creating config.h config.status: executing default-1 commands cd . \ && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status config.status: creating Makefile config.status: executing default-1 commands cd . \ && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status config.status: creating Makefile config.status: executing default-1 commands cd . \ && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status config.status: creating Makefile config.status: executing default-1 commands cd . \ && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status config.status: creating Makefile config.status: executing default-1 commands cd . \ <snip: this repeats a few hundred times> && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status config.status: creating Makefile config.status: executing default-1 commands cd . \ && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status config.status: creating Makefile config.status: executing default-1 commands make: *** creating jobs pipe: Too many open files. Stop. !!! ERROR: dev-libs/libxml2-2.5.6 failed. !!! Function src_compile, Line 37, Exitcode 2 !!! (no error message) Calculating dependencies ...done! >>> emerge (1 of 1) dev-libs/libxml2-2.5.6 to / >>> md5 ;-) libxml2-2.5.6.tar.bz2 Expected Results: Normal compile and install of libxml2 # emerge info Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4) ================================================================= System uname: 2.4.20-openmosix-r4 i586 AMD-K6(tm) 3D processor GENTOO_MIRRORS="http://gentoo.linux.no http://gentoo.oregonstate.edu/ http://www .ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/confi g /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/usr/portage/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm avi crypt cups encode gif java jpeg gnome libg++ libwww m ikmod mmx motif mpeg ncurses nls oggvorbis pdflib png quicktime sdl spell truety pe xmms xv zlib alsa gdbm berkdb slang readline svga X gpm tcpd pam ssl perl pyt hon esd imlib gtk opengl gtk2 ipv6 samba usb -arts -kde -qt -xml2" COMPILER="gcc3" CHOST="i586-pc-linux-gnu" CFLAGS="-march=k6 -O3 -pipe -fomit-frame-pointer" CXXFLAGS="-march=k6 -O3 -pipe -fomit-frame-pointer" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j4" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
Created attachment 12198 [details] Complete output of emerge libxml2
I am not the owner of the computer where the problem was present, and it was needed for other use, so I can't help with more information. I hope I have provided enought information to solve the bug. And again, thanks for a wonderful, and powerful GNU/Linux dist. ;)
hmm .. this is rather bizzare .. never seen anything like this. is it maybe running out of disk space or something? if that is still the problem, can you attach the config.log? that would probably be more useful in this case ..
ok .. i asked around and it seems the only reasonable explaination is that the system clock was wrong. it was behind enough to confuse make/configure into thinking that the files were in the future.. seeing that the box isn't around anymore, i'll close this one now. reopen if you have more information or if you think that isn't the case.
