Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #87839 > unrolled thread
| Started by | Dan Stromberg <drsalists@gmail.com> |
|---|---|
| First post | 2015-03-23 10:36 -0700 |
| Last post | 2015-03-23 10:36 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
Statically linking part of a C extension module? Dan Stromberg <drsalists@gmail.com> - 2015-03-23 10:36 -0700
| From | Dan Stromberg <drsalists@gmail.com> |
|---|---|
| Date | 2015-03-23 10:36 -0700 |
| Subject | Statically linking part of a C extension module? |
| Message-ID | <mailman.76.1427132170.10327.python-list@python.org> |
Hi folks. I want to build a pair of wheels - one for numpy, one for scipy. And I want to statically link atlas (with blas and lapack) into these wheels. I don't want to statically link numpy or scipy into the Python interpreter. The goal is to decrease the frequency with which new wheels need to be built as the OS changes (RHEL 6.6), and to avoid having to deploy rpm's - we want to only deploy wheels if possible. How practical is this? I have some guesses how to do it (passing in $CFLAGS, $LDFLAGS and $CC perhaps), but if there's a better way I'd love to know about it. Thanks!
Back to top | Article view | comp.lang.python
csiph-web