Re: [Numpy-discussion] Numpy Installation Problem on Redhat Linux

2012-07-05 Thread Paul Anton Letnes
Hi, are you sure that you want g77 and not gfortran? If you want gfortran, you should pass the > --fcompiler=gnu95 flag to setup.py. Which redhat version are you building on? (I don't know red hat well enough to comment, but perhaps someone else do...) Paul On 6. juli 2012, at 03:00, Hung-Hsu

[Numpy-discussion] Numpy Installation Problem on Redhat Linux

2012-07-05 Thread Hung-Hsuan Chen
Dear all, I've built blas, lapack, and atlas libraries, as shown below. $ ls ~/lib/atlas/lib/ libatlas.a libcblas.a libf77blas.a liblapack.a libptcblas.a libptf77blas.a The library location are specified by site.cfg file, as shown below. [DEFAULT] library_dirs = /home/username/lib/atlas/li

Re: [Numpy-discussion] Buildbot status

2012-07-05 Thread Ondřej Čertík
Hi Stefan, On Tue, Jul 3, 2012 at 1:59 PM, Stéfan van der Walt wrote: > On Mon, Jul 2, 2012 at 6:31 PM, Travis Oliphant wrote: >> Ondrej should have time to work on this full time in the coming days. > > That's great; having Ondrej on this full time will help a great deal. > >> NumFocus can prov

Re: [Numpy-discussion] f2py with allocatable arrays

2012-07-05 Thread Ondřej Čertík
On Tue, Jul 3, 2012 at 9:51 PM, Paul Anton Letnes wrote: > > On 4. juli 2012, at 02:23, Sturla Molden wrote: > >> Den 03.07.2012 20:38, skrev Casey W. Stark: >>> >>> Sturla, this is valid Fortran, but I agree it might just be a bad >>> idea. The Fortran 90/95 Explained book mentions this in the >>

Re: [Numpy-discussion] f2py with allocatable arrays

2012-07-05 Thread Ondřej Čertík
On Tue, Jul 3, 2012 at 5:27 PM, Sturla Molden wrote: > Den 04.07.2012 01:59, skrev Sturla Molden: >> But neither was the case here. The allocatable was a dummy variable in >> a subroutine's interface, declared with intent(out). That is an error >> the compiler should trap, because it is doomed to

Re: [Numpy-discussion] f2py with allocatable arrays

2012-07-05 Thread Casey W. Stark
Hi all. Thanks for the help again. I ended up going with running it twice -- once for the final number of particles and second for the positions. Sturla, given that this functionality is so standard dependent, I decided to ditch it. It works with my gfortran, but who knows with other machines and

Re: [Numpy-discussion] Preferring gfortran over g77 on OS X and other distributions?

2012-07-05 Thread Ralf Gommers
On Wed, Jun 27, 2012 at 11:26 PM, Aron Ahmadia wrote: > I've promoted gfortran to be the default compiler on OS X over vendor > compilers (to be more compatible with Linux), and made a similar adjustment > for the platform detection. I've promoted gfortran over g77 but not vendor > compilers on

Re: [Numpy-discussion] "import numpy" performance

2012-07-05 Thread Ralf Gommers
On Tue, Jul 3, 2012 at 1:16 AM, Andrew Dalke wrote: > On Jul 3, 2012, at 12:46 AM, David Cournapeau wrote: > > It is indeed irrelevant to your end goal, but it does affect the > > interpretation of what import_array does, and thus of your benchmark > > Indeed. > > > Focusing on polynomial seems th

Re: [Numpy-discussion] Numpy regression in 1.6.2 in deducing the dtype for record array

2012-07-05 Thread Sandro Tosi
On Thu, Jul 5, 2012 at 8:18 AM, Scott Sinclair wrote: > Except that cherry picking the commit to the 1.6.x branch doesn't > apply cleanly. It'll take some work by someone familiar with that part > of the code.. That's actually what I was looking for :) someone knowing that code to backport the fi