Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path: <drsalists@gmail.com>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.007
X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'scipy': 0.05; 'interpreter.': 0.07; 'statically': 0.07; 'deploy': 0.09; 'subject:module': 0.09; 'python': 0.11; 'changes': 0.15; 'atlas': 0.16; 'numpy': 0.16; 'to:name:python list': 0.16; 'this?': 0.23; 'message-id:@mail.gmail.com': 0.30; 'thanks!': 0.32; "i'd": 0.34; 'possible.': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'subject:?': 0.36; 'to:addr:python-list': 0.38; 'to:addr:python.org': 0.39; 'how': 0.40; 'new': 0.61; 'love': 0.65; 'goal': 0.75
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=bGvF1JQ3YtysQV87keovohGyzP87oLNJbrjFBNC7wjk=; b=cuQ/jROZ/TgscIo+LmGurom0j4JV/2buBDp2Tr0NFFJDOS8kR7M39tVzz6E7/RPYmN tei/iE+FjpIYxSk4TUJ8/aoevKlQntwAHmXJoHFYzXCInlH2nkaraSmRpRHZFKNBewXJ p7uR4R6HJxBq/lNPkiASOUjDQc+h94bPEDTBXjcGQL9iEGtCjEgHs2VUIR+/yeVSTPwE JsqznLRLzhwbb6BJSob/WvWMlX8SU/1OHsoBfn5QdhXnbEXMW9o/kP/zhJz6sH/Bxe7f yb5vJlxn9DwF3ByLI5aPEPFDQR5S7l9ydzYrtXLNVtXvBoyS+ajBC/2V74ejUkNbLZWX ISkg==
MIME-Version: 1.0
X-Received: by 10.112.146.70 with SMTP id ta6mr150485lbb.59.1427132165875; Mon, 23 Mar 2015 10:36:05 -0700 (PDT)
Date: Mon, 23 Mar 2015 10:36:05 -0700
Subject: Statically linking part of a C extension module?
From: Dan Stromberg <drsalists@gmail.com>
To: Python List <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.19
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.76.1427132170.10327.python-list@python.org>
Lines: 17
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1427132170 news.xs4all.nl 2877 [2001:888:2000:d::a6]:57056
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:87839

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!