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

Python and bzip2 #122

Closed
lee218llnl opened this issue Oct 7, 2015 · 5 comments
Closed

Python and bzip2 #122

lee218llnl opened this issue Oct 7, 2015 · 5 comments
Assignees

Comments

@lee218llnl
Copy link
Contributor

Python is not building the bz2 module because it is trying to link to the bzip2 package's .a file which was not compiled -fpic. The bzip2 package does build a shared library, but only appears to generate versioned .so files/links, i.e., libbz2.so.1.0 and libbz2.so.1.0.6 and not the generic libbz2.so.

@tgamblin
Copy link
Member

tgamblin commented Oct 8, 2015

@lee218llnl: would adding the symlink fix this? I could add this to the bzip2 package post-make('install'). If not, then we could build the .a with -fpic but I dunno what other packages that might affect (Mark Miller and I kind of talked about this here)

@lee218llnl
Copy link
Contributor Author

Todd, I think adding a symlink will suffice. I will work on this.

@lee218llnl lee218llnl self-assigned this Oct 8, 2015
@sjtbham
Copy link
Contributor

sjtbham commented Dec 2, 2015

@lee218llnl @tgamblin The python package doesn't work properly at the moment. Although it "depends" on openssl, bzip2 etc, it doesn't build the modules for them. (If you have the OS openssl-devel package installed then it will). I've been trying to work out why my python wasn't built correctly and found that if the LDFLAGS and CPPFLAGS aren't set correctly, then setup.py won't find the headers and libraries. As these are normally set by the cc wrapper, they don't end up visible to setup.py.

I'm just testing an updated package for python at the moment, (with some updates for python3 as well).

@sjtbham
Copy link
Contributor

sjtbham commented Dec 2, 2015

@lee218llnl @tgamblin I've added PR 215 which I think resolves the build issues.

@tgamblin
Copy link
Member

Fixed by #215

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