Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/crtbeginT.o: could not read symbols: Bad value #3

Closed
oleiade opened this issue Mar 2, 2012 · 7 comments
Closed

/crtbeginT.o: could not read symbols: Bad value #3

oleiade opened this issue Mar 2, 2012 · 7 comments

Comments

@oleiade
Copy link

oleiade commented Mar 2, 2012

Here's an error I get when I come to python setup.py build. Any ideas of how to resolve it? I use a Fedora system, leveldb and snappy compiled and installed fine.

gcc -pthread -shared build/temp.linux-x86_64-2.7/src/initmodule.o build/temp.linux-x86_64-2.7/src/leveldb.o build/temp.linux-x86_64-2.7/src/write_batch.o build/temp.linux-x86_64-2.7/src/iterator.o build/temp.linux-x86_64-2.7/src/snapshot.o build/temp.linux-x86_64-2.7/src/range_iterator.o -L/usr/lib64 -lpython2.7 -o build/lib.linux-x86_64-2.7/leveldb.so -L./leveldb -static -lleveldb -lsnappy -lpthread
/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/4.6.1/crtbeginT.o: relocation R_X86_64_32 against `DTOR_END' can not be used when making a shared object; recompile with -fPIC
/usr/lib/gcc/x86_64-redhat-linux/4.6.1/crtbeginT.o: could not read symbols: Bad value

@oleiade
Copy link
Author

oleiade commented Mar 2, 2012

Exact same error on debian Squeeze.

@forhappy
Copy link
Owner

forhappy commented Mar 5, 2012

This error depends on your OS platform, cpy-leveldb now has compiling errors on 64 bit OS, I'll fix this bug as soon as possible, thanks for comments.

@oleiade
Copy link
Author

oleiade commented Apr 12, 2012

Up

@carlopires
Copy link
Contributor

I have the same issue here. Any hint on how to fix this?

@oleiade
Copy link
Author

oleiade commented Jun 7, 2012

Up, please fix :-)

@carlopires
Copy link
Contributor

I just added a pull request with a fix for this issue.

@forhappy
Copy link
Owner

forhappy commented Jun 8, 2012

thanks for your patch:)

@oleiade oleiade closed this as completed Oct 17, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants