[Numpy-discussion] Instructions on building from source

Robert Kern robert.kern@gmail....
Thu Jul 24 02:24:07 CDT 2008

On Thu, Jul 24, 2008 at 02:15, Eric Firing <efiring@hawaii.edu> wrote:
> Andrew Straw wrote:
>> Just for reference, you can find the build dependencies of any Debian
>> source package by looking at its .dsc file. For numpy, that can be found
>> at http://packages.debian.org/sid/python-numpy
>> Currently (version 1.1.0, debian version 1:1.1.0-3), that list is:
>> Build-Depends: cdbs (>= 0.4.43), python-all-dev, python-all-dbg,
>> python-central (>= 0.6), gfortran (>= 4:4.2), libblas-dev [!arm !m68k],
>> liblapack-dev [!arm !m68k], debhelper (>= 5.0.38), patchutils,
>> python-docutils, libfftw3-dev
>> Build-Conflicts: atlas3-base-dev, libatlas-3dnow-dev, libatlas-base-dev,
>> libatlas-headers, libatlas-sse-dev, libatlas-sse2-dev
> Do you know why atlas is not used, and is even listed as a conflict?  I
> have libatlas-sse2 etc. installed on ubuntu hardy, and I routinely build
> numpy from source.  Maybe the debian specification is for
> lowest-common-denominator hardware?

Not quite LCD, but that's close to the truth. Basically, a binary
numpy package built against liblapack-dev will work with ATLAS when it
is installed. Is suspect that one built against libatlas-base-dev may
not work without ATLAS installed.

It's specific packaging for Debian-and-spawn, not a general numpy
requirement. Which is one reason why looking at a distribution's
build-deps is not very useful for inferring details about the
dependencies about the upstream packages.

Robert Kern

"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
 -- Umberto Eco

More information about the Numpy-discussion mailing list