Date: | Tue, 14 Jul 2009 16:20:10 +0200 |
---|---|
From: | Daniel Sánchez Pedreño <sanatox@xxxxxxxxx> |
Subject: | Re: [Gems-users] libelf.so.0 and libpython2.4.so problem |
OK, I have already solved my problem. If you do "export LANG=en" (if you are sugin another language) you can see an error related to "relocation R_X86_64_32 can not be used when making a shared object". The solution I found is to add the -fPIC command to CC=g++ in common/Makefile.common. You must be sure to perform a "make clean" and to remove manually the "ruby.o" object before a new attempt. I hope this can be useful to anybody. Chau!!! 2009/7/14 Daniel Sánchez Pedreño <sanatox@xxxxxxxxx> Hi Polina, -- Daniel Sánchez Pedreño <dsanchez@xxxxxxxxxxx> Grupo de Arquitectura y Computación Paralela. Facultad de Informática. Universidad de Murcia. Campus de Espinardo - 30080 Murcia (SPAIN) Tel: +34 868 887656 Fax: +34 868 884151 web: http://skywalker.inf.um.es/~dsanchez |
Previous by Date: | Re: [Gems-users] ATMTP: Problem with strange Transaction-Aborts, Philipp Tölke |
---|---|
Next by Date: | Re: [Gems-users] libelf.so.0 and libpython2.4.so problem, Polina Dudnik |
Previous by Thread: | Re: [Gems-users] libelf.so.0 and libpython2.4.so problem, Daniel Sánchez Pedreño |
Next by Thread: | Re: [Gems-users] libelf.so.0 and libpython2.4.so problem, Polina Dudnik |
Indexes: | [Date] [Thread] |