When trying to emerge dev-libs/glib-2.4.0, configure complains "I can't find the libraries for the thread implementation posix". Reproducible: Always Steps to Reproduce: 1. emerge glib Actual Results: emerge fails, end of output: checking for thread implementation... posix checking thread related cflags... -D_REENTRANT checking for pthread_create/pthread_join... no checking for pthread_create/pthread_join in -lpthread... no checking for pthread_create/pthread_join in -lpthread32... no checking for pthread_create/pthread_join in -lpthreads... no checking for pthread_create/pthread_join in -lthread... no checking for pthread_create/pthread_join in -ldce... no configure: error: I can't find the libraries for the thread implementation posix. Please choose another thread implementation or provide information on your thread implementation. You can also run 'configure --disable-threads' to compile without thread support. !!! ERROR: dev-libs/glib-2.4.0 failed. !!! Function econf, Line 365, Exitcode 1 !!! econf failed Expected Results: emerge should complete properly. System normally runs with Grsec/Pax, however emerge fails with Grsec disabled as well. Portage 2.0.50-r6 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.25-gentoo-r2)================================================================= System uname: 2.4.25-gentoo-r2 i686 Celeron (Mendocino) Gentoo Base System version 1.4.9 ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=i686 -funroll-loops -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /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/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=i686 -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://ftp.tu-clausthal.de/pub/linux/gentoo http://mirrors.sec.informatik.tu-darmstadt.de/gentoo http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X aalib alsa apache2 apm arts async avi berkdb bonobo caps crypt cups curl dga doc encode esd fbcon foomaticdb gd gd-external gdbm ggi gif gnome gpm gstreamer gtk gtk2 gtkhtml guile hbci idea imlib innodb jabber java jikes jpeg kde libg++ libwww mad maildir memlimit mikmod mmx motif mozcalendar mozilla moznocompose moznoirc moznomail mozsvg mpeg mysql nas ncurses nls ofx oggvorbis opengl operanom2 oss pam pdflib perl png python qt quicktime readline samba sdl slang spell sse ssl svga tcltk tcpd tetex tiff truetype usb wmf x86 xml2 xmms xv zlib"
Problem still exists with glib-2.4.1. The same error occurs when configure-ing a vanilla glib-2.4.1, so I suppose it should be reported upstream. Should I do this, or will the Gentoo Linux Gnome Desktop Team do it?
i wouldn't file anything until i figured out that it really isn't a local problem. Does config.log give any clues as to why the posix threads aren't available. Note that you seem to be the only one with this problem...
what version of the kernel headers are you using?
no reply
I encountered the same problem while doing "emerge gnome" inside a chroot install. The running kernel is a suse 2.4.17 (no pax support and probably no thred support?). This is very probably because the test program, while running tries to use threads in the current kernel, which is too old. Booting with the new kernel will probably resolve the issue.
*** Bug 62471 has been marked as a duplicate of this bug. ***
The problem disappeared after emerging glibc-2.3.4.20040808-r1.
*** Bug 89677 has been marked as a duplicate of this bug. ***
