On 5/1/05, Simon Stelling <[EMAIL PROTECTED]> wrote: > Hi! thx for replying!
> > > /[..]/ld: ../../libplayerc.a(mclient.o): relocation R_X86_64_32 > > against `a local symbol' can not > > be used when making a shared object; recompile with -fPIC > > specifying -fPIC with append-flags to it didn't help :( . > > Did you already file a bug? I wrote a tiny ebuild myself . I like to keep things clean. > > I have a running version, built when I had "-fPIC" in make.conf. I > > removed it ca one week ago. Since then i did emerge -vDu world once, > > things like gcc,glibc,pythin or xorg could have gotten rebuilt w/o > > -fPIC. Could this be the problem ? > > No. In fact, you should NOT use -fPIC in your make.conf, that's ugly. > Remove it, be happy, and file bugs if you see a package that needs some > tweaks. I'm a total noob when it comes to such things. Should I do emerge -e world after having removed "-fPIC"?? > > Any idea what should I rebuild to get it up'n'runing? Maybe someone > > knows the R_X86_64_32 symbol ? > > See above, it's better to not have it entirely compiled with -fPIC. Your > shared objects (which is what we want compiled with -fPIC) will > automatically get that flag, otherwise gcc will complain about it with > the error message you pasted. I removed the python bindings and it works. Since I don't really need them it's not a big deal. BTW: First I tried to rebuild python, but I'm getting an error metioned few hours ago on gentoo-user@ about missing file 'glibc'. -- Regards Karol Krzak -- [email protected] mailing list
