checking for NPTL bug... yes !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! You seem to have a buggy PTHREAD library! LinuxSampler would probably crash due to this. Please report us the system you are using and/or file a bug report to the bug tracking system of your distribution. If you have a NPTL-enabled glibc AND it was compiled for TLS as well, you can try to circumvent this problem for now by setting the environment variable LD_ASSUME_KERNEL="2.4.1" , which should cause this test to pass. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Reproducible: Always Steps to Reproduce: 1. emerge media-sound/linuxsampler ================================================================= Package Settings ================================================================= sys-libs/glibc-2.6.1 was built with the following: USE="acl berkdb bindist bitmap-fonts bzip2 cli cracklib crypt cups dri fortran gdbm gpm iconv ipv6 isdnlog midi mudflap ncurses nls nptl nptlonly openmp pam pcre perl pppd python readline reflection session spl ssl tcpd truetype-fonts type1-fonts unicode xorg zlib -debug -gd -glibc-omitfp (-hardened) (-multilib) -profile (-selinux) -vanilla" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" INPUT_DEVICES="evdev keyboard mouse" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i740 i810 imstt mach64 mga neomagic nsc nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo" CFLAGS="-march=i686 -pipe -O2 -fno-strict-aliasing" CXXFLAGS="-march=i686 -pipe -O2 -fno-strict-aliasing" LDFLAGS=""
Created attachment 209385 [details] emerge --info
uname -a Linux defseg 2.6.25-gentoo-r9 #6 Sun Jul 5 04:21:12 PDT 2009 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux
*** This bug has been marked as a duplicate of bug 194076 ***
I agree 100% that the solution to this problem is listed in bug 194076. However, that bug more specifically addresses the problem in gcc itself, and not media-sound/linuxsampler (although it is heavily mentioned as the trigger of the bug). The summary for *this* bug actually addresses "linuxsampler" specifically (a bug search for "linuxsampler" will not find the other bug report). The nptl build-time test (as of 0.5.1) still incorrectly states that this is a glibc bug, when it is actually a gcc bug (you need to emerge >=gcc-4.2.x and run gcc-config to solve the problem), so this is still a bug in the linuxsampler sources, as it should state that a gcc upgrade is needed.
any number of things could cause the test to fail (kernel/hardware/headers/etc...). the test is stating the most common reason, not doing a full diagnosis of your system. upgrade your packages and move on. *** This bug has been marked as a duplicate of bug 194076 ***
If you read bug 194076, then you'll realize that upgrading to >=gcc-4.2 (and running gcc-config) will *always* fix this problem. I still believe this is an upstream bug. I hate lazy maintainers who spend more time flagging bugs as invalid than they do actually fixing problems. Can't you just let it sit in an open state so that maybe someone who cares will take a look at it?!
try reading my last comment again. *your* case might be fixed, but that isnt nearly the same thing as *all* cases. the error output comes from an upstream package, not from a Gentoo ebuild. no one really cares. *** This bug has been marked as a duplicate of bug 194076 ***
I'm done fighting this. If you read *all* of the comments on bug 194076, you'd realize that the solution I mentioned always works (and it will pull in a new glibc automatically if required). A few of the posters (on the other bug) were incorrect about why they were receiving the error (which they eventually realized). That's what caused the confusion of what exactly was the source of the problem. 100% of the people reported that upgrading gcc was what ultimately fixed their problem. Upgrading glibc alone never fixed the problem (read comment #14 down on the other bug to see that gcc, because of a library, did). All I'm requesting is a simple patch to correct the error message, which I would write myself if I didn't have to spend all my time arguing this =) This bug should be marked UPSTREAM with a proper patch attached to it if you really want me to go away.
