Returns: /usr/lib/python2.2/config/libpython2.2.a(abstract.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/lib/python2.2/config/libpython2.2.a: could not read symbols: Bad value Probably, though I haven't checked, I could add -fPIC to my USE variables but this is apparently not an acceptable solution, as per http://dev.gentoo.org/~brad_mssw/amd64-tech-notes.html Reproducible: Always Steps to Reproduce: 1. put an xchat in your overlay, modify so it will emerge 2. try to emerge xchat Actual Results: /usr/lib/python2.2/config/libpython2.2.a(abstract.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/lib/python2.2/config/libpython2.2.a: could not read symbols: Bad value Expected Results: emerged without requiring -fPIC
Ok, you're running an old python ebuild or something. Update your rsync and re-emerge python. That was fixed over 2 weeks ago. -Brad
rsync was up to date (the whole system was only stage1'd yesterday :P). put python-2.2.3-r5 in my overlay as it was the latest stable on my x86 box, (python-2.2.3 was what I had emerged), emerged python-2.2.3-r5, tried the xchat-2.0.5-r1 ebuild again, worked flawlessly. Perhaps python-2.2.3-r5 should be "amd64"? Should I submit a bug report for python on amd64?
hmm, thought it was marked stable, guess not, just committed it as stable to cvs, so an rsync in about 1/2 hour will have it I do recommend using ACCEPT_KEYWORDS="~amd64" in you make.conf though, as most packages are in that category ... -Brad
