[Numpy-discussion] Bus error for Debian / SPARC on current trunk

Charles R Harris charlesr.harris@gmail....
Mon Mar 5 07:50:16 CST 2012


On Mon, Mar 5, 2012 at 1:20 AM, Travis Oliphant <travis@continuum.io> wrote:

>
> The place this is used inside of setup.py is here:
>
> https://github.com/numpy/numpy/blob/master/numpy/core/setup.py#L14
>
> I really dislike this build feature, it repeatedly trips me up. In my
> opinion, the build should be changed to always do separate compilation, and
> the single file mode should be eradicated.
>
>
> Nobody *likes* this build "feature".   If it can be eradicated let's do
> it, but when I wanted to early on I couldn't for various reasons.   I'm not
> convinced these reasons have been addressed.
>
>
This was David's contribution and wasn't put in, IIRC,  until the files
were broken up in 1.3. The reason it isn't standard is that it was
experimental at the time.


> The big problem I had (if I remember correctly) was getting the NumPy
> C-API to be exportable on all platforms (yet having the variables be static
> and hidden from the shared symbol-space) if it was assembled from multiple
> files.   The NumPy C-API uses a clever trick that was invented for Python
> back in the late 90s which was important for getting extensions that used
> the NumPy C-API to work on several platforms.
>
> If we can be assured that platforms that might have needed that are no
> longer needing NumPy (or there are work-arounds), then we can certainly get
> rid of a single-file build mode.
>
>
We should probably make is standard for a while to see if it causes
problems.

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20120305/a1e53730/attachment-0001.html 


More information about the NumPy-Discussion mailing list