There were two problems. First, numpy ignored my export
ATLAS=/usr/local/atlas. setup.py printed out the directories it was
searching and it just searched the defaults then said it couldn't find
ATLAS.
I 'fixed' that problem by adding symlinks in the default directories.
Now I get error messages l
On Wed, Oct 20, 2010 at 09:13:24AM -0400, Ian Goodfellow wrote:
>--with-netlib-lapack is indeed no longer valid.
>INSTALL.txt includes a warning that INSTALL.txt is out of date, you should
>refer to doc/atlas_install.pdf instead.
Ah, I read too quickly and missed that. Thanks.
>Th
--with-netlib-lapack is indeed no longer valid.
INSTALL.txt includes a warning that INSTALL.txt is out of date, you should
refer to doc/atlas_install.pdf instead.
The new option is --with-netlib-lapack-tarfile
I successfully built 3.9.25 with this option a while ago, but haven't been
able to get nu
On Wed, Oct 20, 2010 at 11:59:24AM +0300, Pearu Peterson wrote:
> I haven't build atlas libraries for awhile and may be something
> is changed in atlas.. That said, I would try instructions from
> http://www.scipy.org/Installing_SciPy/Linux#head-89e1f6afaa3314d98a22c79b063cceee2cc6313c
That was m
On 10/20/2010 11:48 AM, Gael Varoquaux wrote:
> On Wed, Oct 20, 2010 at 04:41:38PM +0900, David wrote:
>>> - ldd /volatile/varoquau/dev/numpy/numpy/linalg/lapack_lite.so: does it
>>> load the libraries you think are you loading ?
>
> For the dynamic libraries, it seems so. I am using static l
On Wed, Oct 20, 2010 at 04:41:38PM +0900, David wrote:
> > - ldd /volatile/varoquau/dev/numpy/numpy/linalg/lapack_lite.so: does it
> > load the libraries you think are you loading ?
For the dynamic libraries, it seems so. I am using static libraries for
atlas/blas (.a)
> > - nm atlas_libr
On Wed, Oct 20, 2010 at 09:43:12AM +0200, Gael Varoquaux wrote:
> On Wed, Oct 20, 2010 at 09:38:25AM +0200, Gael Varoquaux wrote:
> > Hum, this page is mentionning a '--with-netlib-lapack' swith the the
> > configre that is not in the INSTALL.txt of my atlas version.
> OK, that's no longer valid.
On Wed, Oct 20, 2010 at 09:38:25AM +0200, Gael Varoquaux wrote:
> Hum, this page is mentionning a '--with-netlib-lapack' swith the the
> configre that is not in the INSTALL.txt of my atlas version.
OK, that's no longer valid.
However, I just realize that atlas now packages the netlib lapack in t
On 10/20/2010 04:39 PM, David wrote:
> On 10/20/2010 04:23 PM, Gael Varoquaux wrote:
>> I am really sorry to be landing on the mailing list with Atlas build
>> issues. I usually manage be myself to build Atlas, but this time I have
>> been fighting for a couple of days with little success.
>>
>> Th
On 10/20/2010 04:23 PM, Gael Varoquaux wrote:
> I am really sorry to be landing on the mailing list with Atlas build
> issues. I usually manage be myself to build Atlas, but this time I have
> been fighting for a couple of days with little success.
>
> The reason I need to build Atlas is that our w
On Wed, Oct 20, 2010 at 10:32:48AM +0300, Pearu Peterson wrote:
> I could not read the stdout
Because I forgot to attach it! I added it
>but perhaps you didn't build atlas with complete lapack.
That's quite possible. The size of liblapack.a seems a bit too small
(1.1M). On the system for which i
On 10/20/2010 10:23 AM, Gael Varoquaux wrote:
> I am really sorry to be landing on the mailing list with Atlas build
> issues. I usually manage be myself to build Atlas, but this time I have
> been fighting for a couple of days with little success.
>
> The reason I need to build Atlas is that our
I am really sorry to be landing on the mailing list with Atlas build
issues. I usually manage be myself to build Atlas, but this time I have
been fighting for a couple of days with little success.
The reason I need to build Atlas is that our work computers are stuck on
Mandriva 2008.0, in which th
13 matches
Mail list logo
