Gentoo Archives: gentoo-alpha

From: "José Luis Rivero (yoswink)" <yoswink@g.o>
To: gentoo-alpha@l.g.o
Subject: Re: [gentoo-alpha] Problems with Squid
Date: Tue, 30 Jan 2007 18:08:41
Message-Id: 45BF979A.80605@gentoo.org
In Reply to: [gentoo-alpha] Problems with Squid by Andrew Gaylard
Andrew Gaylard escribió:
> Hello gentoo alpha people, > > I've noticed a problem starting up squid on my Miata box: > > Jan 30 02:47:01 supper squid[6558]: Squid Parent: child process 6560 started > Jan 30 02:47:01 supper (squid): comm_select_init: epoll_create(): (78) > Function not implemented
[snip]
> > The system's up to date as far as I can tell: > > net-proxy/squid-2.6.7 > sys-libs/glibc-2.3.6-r4 > sys-devel/gcc-3.4.6-r2 > sys-kernel/linux-headers-2.6.11-r4 > > What am I missing? > > Andrew
I'm also able to reproduce the failure. The situation, as far as I can see,is as follow: The problem was reported in bug #160637[1]. The maintainer solution[2] applied was patch the ebuild to check if epoll support was enabled in the kernel. Ebuild works just fine, detecting if the kernel has the epoll support enabled[3] and adding the proper --enable-epoll in that case. So if the kernel has support for it, the problem should be in a different place, probably glibc or linux-headers. I found a test case[4] you can run just compiling it. Later, I'll reopen the bug and see if one of our toolchain ninjas can give it a try. As a workaround, you can disable the epoll support commenting out the "myconf ..." line in the ebuild (not tested but should work). Thanks for reporting, Regards. -- Jose Luis Rivero <yoswink@g.o> Gentoo/Doc Gentoo/Alpha [1] http://bugs.gentoo.org/show_bug.cgi?id=160637 [2] ------------------- if kernel_is ge 2 6 && linux_chkconfig_present EPOLL ; then myconf="${myconf} --enable-epoll" fi ------------------- [3] # grep 'CONFIG_EPOLL' /usr/src/linux/.config [4] http://www.xmailserver.org/linux-patches/pipetest.c -- gentoo-alpha@g.o mailing list

Replies

Subject Author
Re: [gentoo-alpha] Problems with Squid Andrew Gaylard <ag@××××××××.org>