[Numpy-discussion] Numpy 1.4.1 fails to build on (Debian) alpha and powepc

Sandro Tosi morph@debian....
Thu Jul 29 16:47:24 CDT 2010

sorry it took so long to reply.

On Thu, Jul 29, 2010 at 03:27, David Cournapeau <cournape@gmail.com> wrote:
> On Wed, Jul 28, 2010 at 12:36 AM, Sandro Tosi <morph@debian.org> wrote:
>> On Tue, Jul 27, 2010 at 14:52, Sandro Tosi <morph@debian.org> wrote:
>>> Hi,
>>> On Tue, Jul 27, 2010 at 12:28, David Cournapeau <cournape@gmail.com> wrote:
>>>> On Tue, Jul 20, 2010 at 3:44 AM, Sandro Tosi <morph@debian.org> wrote:
>>>>> ah if you say so, I trust you :)
>>>> Could you try the last version of the trunk, I added the missing
>>>> macros for alpha ?
>>> I just built trunk (both for 2.5 and 2.6) on alpha, successfully :)
>>> Now I'll extract only the needed patch (I think it's enough to apply
>>> r8526, right?) and try to build the package using 1.4.1+patch, if it
>>> builds successfully I'll upload numpy in Debian again.
>> and indeed it build! yay \o/
>>> David, let me thank you very very much for your support!!
>> Renew the great THANK YOU!
> If possible, I would really like to get build and test output logs for
> both alpha/ppc.

For the build logs it's easy:

alpha: https://buildd.debian.org/fetch.cgi?pkg=python-numpy&arch=alpha&ver=1%3A1.4.1-4&stamp=1280296333&file=log&as=raw
powerpc: https://buildd.debian.org/fetch.cgi?pkg=python-numpy&arch=powerpc&ver=1%3A1.4.1-4&stamp=1280297029&file=log&as=raw

for powerpc "import numpy; numpy.test()" I've already sent you the
output, want me to re-run them? for alpha, attached you can find the
log for both 2.5 and 2.6; there are some errors/warnings but nothing
too dramatic?

> Also, if there is another issue preventing numpy 1.4.x integration on
> debian and ubuntu, please speak up. Ideally, I would like to remove

I don't think there is anything else (for now :) ) from the numpy
side: Thanks a lot for the support!! Now on Debian we have to fix some
packages to avoid breakages when we upgrade numpy in the future (the
biggest issue was that dtype was extended with new fields at the end,
but some packages were checking the size of dtype with the one the
packge was compiled with (1.3.*) and failed). As usual, Ubuntu will
just sit and wait for us to do the work and then just sync it (sigh).

> the need for downstream patches (none of them was necessary IIRC),

Here is the list of the patches we currently have in the Debian
package (you can look at them at [2]):

- Patch to build _dotblas.c when ATLAS is not installed.
-- dunno exactly what it does, it seems to infer _dotblas is compiled
is ATLAS is missing

- force generation f2py postfixed with interpreter version
-- Debian specific: we ship f2py2.5 and f2py2.6 and we make f2py a
symlink towards f2py2.6

- Fix endianness detection: endian.h should be present on all Debian
machines. This patch forces the use of endian.h, this reventing
several reverse dependencies os Numpy from failing to build.
-- Debian specific: we want to enforce the usage of endian.h file
available on all of our architectures

- Remove string exceptions
-- patch from trunk, we can remove it once a new release is out

- Use a local copy of object.inv from doc.python.org, instead of
downloading it each time from the internet
-- Debian specific, we are not allowed to download stuff from internet
when building package, so I just download object.inv from d.p.o and
use it in interpshinx_mapping

- support for powerpc
-- patch from trunk, we can remove it once a new release is out

- support for alpha
- patch from trunk, we can remove it once a new release is out

[2] http://svn.debian.org/viewsvn/python-modules/packages/numpy/trunk/debian/patches/

In case of any doubts or so, don't hesitate to contact me: I'd be more
than happy to give all the help I can.

Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: testlog2.5.bz2
Type: application/x-bzip2
Size: 1797 bytes
Desc: not available
Url : http://mail.scipy.org/pipermail/numpy-discussion/attachments/20100729/150f5969/attachment.bz2 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: testlog26.bz2
Type: application/x-bzip2
Size: 626 bytes
Desc: not available
Url : http://mail.scipy.org/pipermail/numpy-discussion/attachments/20100729/150f5969/attachment-0001.bz2 

More information about the NumPy-Discussion mailing list