libstdc++.so.6: cannot handle TLS

[homry]

hi there,

i am pretty new to planeshift and tried to install it on my gentoo system. i installed PS from the binaries offered on this page. now i see there is an extra thread for an ebuild for gentoo in these forums. but i think my problem is not related to wether i take an ebuild or not. when running psclient i will get:

Code: [Select]

./psc: error while loading shared libraries: libstdc++.so.6: cannot handle TLSglxgears works like a charm, so 3d acc seems to work just fine. what can i do about this? thanks

homry

[Bereror]

Looks like you are either using the 2.4 kernel (hard to believe), or managed to build your system without the nptl support, or are using masked packages that may break some compatibility.

Just out of curiosity, run emerge --info and post the output here. You can also try building PS using the Gentoo ebuild.

[homry]

hello and thanks for the reply,

1. i use the 2.6 kernel

2. emerge --info gives me a lot and i would love to post it here, but apperently this is not possible. i do not know why, but i get an error with something like permission denied. what info do you need from this output?

3. my package.keywords:

Code: [Select]

media-video/vlc ~x86
rox-base/rox ~x86
x11-wm/fvwm ~x86
app-emulation/vmware-server ~x86
media-gfx/picasa ~x86
net-www/mplayerplug-in ~x86
x11-drivers/ati-drivers ~x86
net-wireless/ipw2200 ~x86
net-wireless/ipw2200-firmware ~x86
net-wireless/ieee80211 ~x86
4. which ebuild should i use. the one in the tree is masked two times (i could remove one..keywords, but the second) or the ebuild which is tested here in the forums?

thanks,

homry

[Bereror]

2. emerge --info gives me a lot and i would love to post it here, but apperently this is not possible. i do not know why, but i get an error with something like permission denied. what info do you need from this output?

Post the first line with gcc/glibc version numbers and then also the USE flags section. ACCEPT_KEYWORDS might be also interesting to see.
 

4. which ebuild should i use. the one in the tree is masked two times (i could remove one..keywords, but the second) or the ebuild which is tested here in the forums?

Use the one from the forums here. The version in the portage is old and actualy should be removed.

[homry]

Code: [Select]

Portage 2.1.1-r2 (default-linux/x86/no-nptl, gcc-4.1.1, glibc-2.3.6-r5, 2.6.18-gentoo-r3 i686)


Code: [Select]

ACCEPT_KEYWORDS="x86"

Code: [Select]

USE="x86 X acpi alsa apm bash-completion berkdb bitmap-fonts bzlib cli cracklib crypt dlloader
doc dri dvdr elibc_glibc emboss encode fbcon foomaticdb fortran gdbm gif gpm gstreamer gtk gtk2
sdl session spell spl sse sse2 ssl szip

Code: [Select]

tcpd truetype truetype-fonts type1-fonts unicode userland_GNU video_cards_ati video_cards_fbdev
video_cards_fglrx video_cards_radeon video_cards_vesa vorbis wifi xml xorg xpm xv zlib"

[homry]

there are some more useflags i have, but it is a mystery to me how to post them. i always get an error, when trying to post them.

[Bereror]

Portage 2.1.1-r2 (default-linux/x86/no-nptl

Yep, your system is built without the nptl support. Any specific reasons why you are using the no-nptl profile?

I guess your only option is to build PS using the ebuild from the forums here.

[Xordan]

Well he could switch profile and recompile... nptl is default on gentoo now and for a good reason.

[homry]

in my make.conf i have the nptl useflag. and my gentoo installation is pretty new and pretty standard, so i do not understand why i have no nptl support.

homry

[homry]

ok, i have it. make.profile is linked to ..../no-nptl. i guess i will change the profile and recompile. thanks.

homry

[homry]

hi there,

after changing the profile glibc wouldnt recompile with nptl support, cause of my CHOST variable (it was on 386). so i had to change CHOST which is not a standard procedure or at least should not be . i changed it and had to do an emerge -e world. now it is through and i tried to start psclient. it seems to work fine, at least i saw the login screen. but before i continue having adventures with PS....is there another reason expect package managment to use the ebuild, cause right now i am running the binaries from here? thanks

homry

[Bereror]

....is there another reason expect package managment to use the ebuild, cause right now i am running the binaries from here? thanks

There is no simple and easy answer to your question. Is there a reason to build everything from sources like your (and my) Gentoo system is built? Wouldn't it be easier to install Ubuntu or Fedora Core or whatever?

The binary is built with -march=i586 to make sure that it runs on a wide range of different systems. I'm not familiar with the ebuild because I have built everything from CVS sources, but I saw couple of sed commands there, so I guess it will use the compiler settings that you have specified in your make.conf file.

My optimized PS client is built with -march=pentium4 and -msse3. Compared to the official binary version it runs really smooth and fast, so assuming that the ebuild takes care of compiler switches, I would guess the result is much better than the official binary.

[Xordan]

Yeah, the 32-bit binary is i686 actually, but same difference. The binary is designed for compatibility and ease of use rather than speed, although the 64-bit client is compiled for speed too by default. Compiling yourself will get you a faster client, the ebuild will probably have the same effect. In future we'll probably spend some time making everything more 'standard' in the sense that our config files are put in the right place and such (so we can have per user settings for example). Then it'll be easy to get an official ebuild put in portage.

[Induane]

Because my wife and I both play I scripted in per user settings already so that we have our settings and passwords saved.

All I did was create a .planeshift directory in both of our home folders.  Then I moved the config files to that directory for both of us.  I don't have the script in front of my as I'm at work but basically in my psclient launcher script I had a manual rm of all config files in the ps directory just in case, then a  ln -s $HOME/.planeshift/configilename.cfg /opt/planeshift_cvs/planeshift  for each of the config files, then had the script launch psclient.  Worked just fine. 

[Xordan]

hmm, yes that's a good idea. What we need is some way to do it automatically, so without any user input, and make sure that any files that need updating can get updated by us without changing any user settings. The new VFS should help us once that's finished in CS, then I'll look at doing some moving around of things so we can get such a system working. I'd like for settings to be made user specific in windows too (so stored in Application Settings per user).