headers
Michael Hoffman | 1 Jul 01:49
Picon
Favicon

Re: Building numpy 1.0.3-2 on Linux 2.6.8 i686 (Debian 3.1)

David Cournapeau wrote:
> Michael Hoffman wrote:
>> Hi. I have been trying to build NumPy on a 32-bit Linux box using python 
>> setup.py build. I received the following errors:
 >> [...]
 >
> Which distribution are you building on ?

Which Linux distribution? Debian 3.1.
--

-- 
Michael Hoffman
Permalink | Reply | 3 comments |
headers
David Cournapeau | 1 Jul 13:50
Picon
Picon

Re: Building numpy 1.0.3-2 on Linux 2.6.8 i686 (Debian 3.1)

Michael Hoffman wrote:
> David Cournapeau wrote:
>> Michael Hoffman wrote:
>>> Hi. I have been trying to build NumPy on a 32-bit Linux box using python 
>>> setup.py build. I received the following errors:
>  >> [...]
>  >
>> Which distribution are you building on ?
>
> Which Linux distribution? Debian 3.1.
Mmh, 3.1 is sarge, which has python2.4 as default, right ? There may be 
a mismatch somewhere... Particularly since you have two python include 
path (/nfs/acari/mh5/include/python2.5  and 
/software/python-2.5/include/python2.5) which are non standart. Are you 
using those on purpose ? Why not the debian python devel package (do you 
use your own compiled python ?)

David
Permalink | Reply | 2 comments |
headers
John Cartwright | 2 Jul 00:10
Picon

Re: problem compiling v.1.0.3 on a Mac

Hello Robert,

just a followup - I found that I could compile with a stand-alone  
python 2.5 installation, but could not with a 2.5 framework install.   
Same problem as listed below.

Thanks for any help that you can provide.

--john

On Jun 30, 2007, at 2:42 PM, Robert Kern wrote:

> John Cartwright wrote:
>> Hello All,
>>
>> I'm having trouble compile  on a Mac 10.4.10.  It seems as if it's
>> not finding /usr/include:
>>
>> ...
>>                   from /Library/Frameworks/Python.framework/Versions/
>> 2.4/include/python2.4/Python.h:81,
>>                   from _configtest.c:2:
>> /usr/include/stdarg.h:4:25: error: stdarg.h: No such file or  
>> directory
>> ...
>>
>> I tried setting the "CFLAG=-I/usr/include", but w/o success.  Can
>> anyone help me?
>
> It should build out-of-box. Is this the standard Python
(Continue reading)

Permalink | Reply | 6 comments |
headers
Robert Kern | 2 Jul 00:19
Picon
Gravatar

Re: problem compiling v.1.0.3 on a Mac

John Cartwright wrote:
> Hello Robert,
> 
> just a followup - I found that I could compile with a stand-alone  
> python 2.5 installation, but could not with a 2.5 framework install.   
> Same problem as listed below.

By framework install, you mean the distribution from www.python.org? or did you
compile it yourself?

> Thanks for any help that you can provide.

I'd like to, but you will have to provide the information I asked for.

--

-- 
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
Permalink | Reply | 5 comments |
headers
John Cartwright | 2 Jul 00:28
Picon

Re: problem compiling v.1.0.3 on a Mac

Thanks for the prompt reply!  By "framework install" I mean the Mac  
OS X universal installer at www.python.org.  By "stand-alone"  I mean  
compiled from the source tarball at the same site.

--john

On Jul 1, 2007, at 4:19 PM, Robert Kern wrote:

> John Cartwright wrote:
>> Hello Robert,
>>
>> just a followup - I found that I could compile with a stand-alone
>> python 2.5 installation, but could not with a 2.5 framework install.
>> Same problem as listed below.
>
> By framework install, you mean the distribution from  
> www.python.org? or did you
> compile it yourself?
>
>> Thanks for any help that you can provide.
>
> I'd like to, but you will have to provide the information I asked for.
>
> -- 
> 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
(Continue reading)

Permalink | Reply | 4 comments |
headers
Robert Kern | 2 Jul 00:38
Picon
Gravatar

Re: problem compiling v.1.0.3 on a Mac

John Cartwright wrote:
> Thanks for the prompt reply!  By "framework install" I mean the Mac  
> OS X universal installer at www.python.org.  By "stand-alone"  I mean  
> compiled from the source tarball at the same site.

Okay, now can you give us the output of

  $ python setup.py -v build

?

--

-- 
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
Permalink | Reply | 3 comments |
headers
John Cartwright | 2 Jul 01:31
Picon

Re: problem compiling v.1.0.3 on a Mac

I tried to send that last night, but the message was so large that  
it's waiting for approval.  Here's the first part of the output:

Running from numpy source directory.
non-existing path in 'numpy/distutils': 'site.cfg'
F2PY Version 2_3844
blas_opt_info:
( library_dirs = /Library/Frameworks/Python.framework/Versions/2.5/ 
lib:/usr/local/lib:/usr/lib )
   FOUND:
     extra_link_args = ['-Wl,-framework', '-Wl,Accelerate']
     define_macros = [('NO_ATLAS_INFO', 3)]
     extra_compile_args = ['-faltivec', '-I/System/Library/Frameworks/ 
vecLib.framework/Headers']

lapack_opt_info:
( library_dirs = /Library/Frameworks/Python.framework/Versions/2.5/ 
lib:/usr/local/lib:/usr/lib )
   FOUND:
     extra_link_args = ['-Wl,-framework', '-Wl,Accelerate']
     define_macros = [('NO_ATLAS_INFO', 3)]
     extra_compile_args = ['-faltivec']

running build
running config_cc
unifing config_cc, config, build_clib, build_ext, build commands -- 
compiler options
running config_fc
unifing config_fc, config, build_clib, build_ext, build commands -- 
fcompiler options
(Continue reading)

Permalink | Reply | 2 comments |
headers
Mathew | 2 Jul 01:49
Favicon

Re: problem compiling v.1.0.3 on a Mac

John Cartwright wrote:
> I tried to send that last night, but the message was so large that  
> it's waiting for approval.  Here's the first part of the output:
>   
Same for me. Here is the beginning of mine
Running from numpy source directory.
F2PY Version 2_3875
blas_opt_info:
blas_mkl_info:
( library_dirs = /u/vento0/myeates/lib )
( include_dirs = /u/vento0/myeates/include )
(paths: )
(paths: )
(paths: )
(paths: )
(paths: )
(paths: )
  libraries mkl,vml,guide not found in /u/vento0/myeates/lib
  NOT AVAILABLE

atlas_blas_threads_info:
Setting PTATLAS=ATLAS
( library_dirs = /u/vento0/myeates/lib )
(paths: )
(paths: )
(paths: /u/vento0/myeates/lib/libptf77blas.a)
(paths: )
(paths: /u/vento0/myeates/lib/libptcblas.a)
(paths: )
(paths: /u/vento0/myeates/lib/libatlas.a)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andrew Jaffe | 2 Jul 17:32
Picon
Gravatar

Re: how do I configure with gfortran

This is slightly off-topic, but probably of interest to anyone reading 
this thread:

Is there any reason why we don't use --fcompiler=gfortran as an alias 
for --fcompiler=gfortran (and --fcompiler=g77 as an alias for 
--fcompiler=gnu, for that matter)?

Those seem to me to be much more mnemonic names...

Andrew

Robert Kern wrote:
> Christopher Hanley wrote:
>> I have found that setting my F77 environment variable to gfortran is 
>> also sufficient.
>>
>>  > setenv F77 gfortran
>>  > python setup.py install
> 
> That might work okay for building scipy and other packages that only actually
> have FORTRAN-77 code; however, I suspect that Matthew is trying to build
> something with Fortran 90+.
Permalink | Reply | 3 comments |
headers
Andrew Jaffe | 2 Jul 18:02
Picon
Gravatar

Re: how do I configure with gfortran

I wrote:

> This is slightly off-topic, but probably of interest to anyone reading 
> this thread:
> 
> Is there any reason why we don't use --fcompiler=gfortran as an alias 
> for --fcompiler=gfortran (and --fcompiler=g77 as an alias for 
> --fcompiler=gnu, for that matter)?

But, sorry, of course this should be:

   Is there any reason why we don't use --fcompiler=gfortran as an alias
   for --fcompiler=gnu95?

> Those seem to me to be much more mnemonic names...

Andrew
Permalink | Reply | 2 comments |

Gmane