gmane.comp.python.enthought.devel

Jaap Spies | 1 Dec 20:41

Re: Installing ETS-3.0.3 in Sage

bryce hendrix wrote:
> Jaap Spies wrote:
>> bryce hendrix wrote:

> 
> Strangely, distutils used the X11 headers, but didn't bother to link 
> with the X11 library. You might have success setting your LD_FLAGS 
> environment variable, "LD_FLAGS=-lX11", then rebuilding Enable.
> 

Rebuilding with "LD_FLAGS=-lX11" gives the same result :(

Jaap

> Bryce
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Enthought-dev mailing list
> Enthought-dev@...
> https://mail.enthought.com/mailman/listinfo/enthought-dev

headers

Robert Kern | 2 Dec 00:06

Re: Installing ETS-3.0.3 in Sage

On Mon, Dec 1, 2008 at 13:41, Jaap Spies <j.spies@...> wrote:
> bryce hendrix wrote:
>> Jaap Spies wrote:
>>> bryce hendrix wrote:
>
>>
>> Strangely, distutils used the X11 headers, but didn't bother to link
>> with the X11 library. You might have success setting your LD_FLAGS
>> environment variable, "LD_FLAGS=-lX11", then rebuilding Enable.
>>
>
> Rebuilding with "LD_FLAGS=-lX11" gives the same result :(

That's because the correct environment variable would be spelled
LDFLAGS. However, that's not a very good way to let those flags. This
is better:

  $ python setup.py build_ext -lX11 build

However, there are probably more flags missing. I'll take a closer
look at your build log.

--

-- 
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

(Continue reading)

headers

Jaap Spies | 2 Dec 00:10

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:
> On Mon, Dec 1, 2008 at 13:41, Jaap Spies <j.spies@...> wrote:
>> bryce hendrix wrote:
>>> Jaap Spies wrote:
>>>> bryce hendrix wrote:
>>> Strangely, distutils used the X11 headers, but didn't bother to link
>>> with the X11 library. You might have success setting your LD_FLAGS
>>> environment variable, "LD_FLAGS=-lX11", then rebuilding Enable.
>>>
>> Rebuilding with "LD_FLAGS=-lX11" gives the same result :(
> 
> That's because the correct environment variable would be spelled
> LDFLAGS. However, that's not a very good way to let those flags. This
> is better:
> 
>   $ python setup.py build_ext -lX11 build
> 
> However, there are probably more flags missing. I'll take a closer
> look at your build log.
> 

Thanks!

Jaap

headers

Robert Kern | 2 Dec 00:12

Re: Installing ETS-3.0.3 in Sage

On Mon, Dec 1, 2008 at 17:10, Jaap Spies <j.spies@...> wrote:
> Robert Kern wrote:
>> On Mon, Dec 1, 2008 at 13:41, Jaap Spies <j.spies@...> wrote:
>>> bryce hendrix wrote:
>>>> Jaap Spies wrote:
>>>>> bryce hendrix wrote:
>>>> Strangely, distutils used the X11 headers, but didn't bother to link
>>>> with the X11 library. You might have success setting your LD_FLAGS
>>>> environment variable, "LD_FLAGS=-lX11", then rebuilding Enable.
>>>>
>>> Rebuilding with "LD_FLAGS=-lX11" gives the same result :(
>>
>> That's because the correct environment variable would be spelled
>> LDFLAGS. However, that's not a very good way to let those flags. This
>> is better:
>>
>>   $ python setup.py build_ext -lX11 build
>>
>> However, there are probably more flags missing. I'll take a closer
>> look at your build log.
>>
>
> Thanks!

Can you show me the output of the following:

>>> from numpy.distutils.system_info import get_info
>>> get_info('x11')

--

--

(Continue reading)

headers

Jaap Spies | 2 Dec 00:20

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:
> On Mon, Dec 1, 2008 at 17:10, Jaap Spies <j.spies@...> wrote:
>> Robert Kern wrote:
>>> On Mon, Dec 1, 2008 at 13:41, Jaap Spies <j.spies@...> wrote:
>>>> bryce hendrix wrote:
>>>>> Jaap Spies wrote:
>>>>>> bryce hendrix wrote:
>>>>> Strangely, distutils used the X11 headers, but didn't bother to link
>>>>> with the X11 library. You might have success setting your LD_FLAGS
>>>>> environment variable, "LD_FLAGS=-lX11", then rebuilding Enable.
>>>>>
>>>> Rebuilding with "LD_FLAGS=-lX11" gives the same result :(
>>> That's because the correct environment variable would be spelled
>>> LDFLAGS. However, that's not a very good way to let those flags. This
>>> is better:
>>>
>>>   $ python setup.py build_ext -lX11 build
>>>
>>> However, there are probably more flags missing. I'll take a closer
>>> look at your build log.
>>>
>> Thanks!
> 
> Can you show me the output of the following:
> 
>>>> from numpy.distutils.system_info import get_info
>>>> get_info('x11')
> 

[jaap <at> paix sage-3.2.1.rc0]$ ./sage -wthread

(Continue reading)

headers

Jaap Spies | 2 Dec 00:24

Re: Installing ETS-3.0.3 in Sage

Jaap Spies wrote:

> 
> [jaap <at> paix sage-3.2.1.rc0]$ ./sage -wthread
> ----------------------------------------------------------------------
> | Sage Version 3.2.1.rc0, Release Date: 2008-11-29                   |
> | Type notebook() for the GUI, and license() for information.        |
> ----------------------------------------------------------------------
> 
> sage: from numpy.distutils.system_info import get_info
> 
> sage: get_info('x11')
>   {}
> 
> 

[jaap <at> paix sage-3.2.1.rc0]$ ipython
sage: from numpy.distutils.system_info import get_info
sage: get_info('x11')
  _2 = {}

Jaap

> Jaap
> 
> 
> 
> _______________________________________________
> Enthought-dev mailing list
> Enthought-dev@...

(Continue reading)

headers

Robert Kern | 2 Dec 00:24

Re: Installing ETS-3.0.3 in Sage

On Mon, Dec 1, 2008 at 17:20, Jaap Spies <j.spies@...> wrote:

> sage: from numpy.distutils.system_info import get_info
>
> sage: get_info('x11')
>  {}

And that's your problem. Where are your X11 libraries and headers?

--

-- 
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

headers

Jaap Spies | 2 Dec 00:33

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:
> On Mon, Dec 1, 2008 at 17:20, Jaap Spies <j.spies@...> wrote:
> 
>> sage: from numpy.distutils.system_info import get_info
>>
>> sage: get_info('x11')
>>  {}
> 
> And that's your problem. Where are your X11 libraries and headers?
> 

On the standard place, I suppose. Where else would Fedora keep them?

Jaap

Ok, I'll look into that.

headers

Robert Kern | 2 Dec 00:35

Re: Installing ETS-3.0.3 in Sage

On Mon, Dec 1, 2008 at 17:33, Jaap Spies <j.spies@...> wrote:
> Robert Kern wrote:
>> On Mon, Dec 1, 2008 at 17:20, Jaap Spies <j.spies@...> wrote:
>>
>>> sage: from numpy.distutils.system_info import get_info
>>>
>>> sage: get_info('x11')
>>>  {}
>>
>> And that's your problem. Where are your X11 libraries and headers?
>
> On the standard place, I suppose. Where else would Fedora keep them?

On 64-bit platforms, it keeps the libraries in /usr/lib64/ instead.

--

-- 
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

headers

Jaap Spies | 2 Dec 00:40

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:
> On Mon, Dec 1, 2008 at 17:33, Jaap Spies <j.spies@...> wrote:
>> Robert Kern wrote:
>>> On Mon, Dec 1, 2008 at 17:20, Jaap Spies <j.spies@...> wrote:
>>>
>>>> sage: from numpy.distutils.system_info import get_info
>>>>
>>>> sage: get_info('x11')
>>>>  {}
>>> And that's your problem. Where are your X11 libraries and headers?
>> On the standard place, I suppose. Where else would Fedora keep them?
> 
> On 64-bit platforms, it keeps the libraries in /usr/lib64/ instead.
> 

Here in 32 bits in /usr/lib:

[jaap <at> paix lib]$ ls libX*
libX11.so               libXfixes.so.3          libXrender.so.1
libX11.so.6             libXfixes.so.3.1.0      libXrender.so.1.3.0
libX11.so.6.2.0         libXfontcache.so        libXRes.so
libX11-xcb.so           libXfontcache.so.1      libXRes.so.1
libX11-xcb.so.1         libXfontcache.so.1.0.0  libXRes.so.1.0.0
libX11-xcb.so.1.0.0     libXfont.so             libXss.so
libXau.so               libXfont.so.1           libXss.so.1
libXau.so.6             libXfont.so.1.4.1       libXss.so.1.0.0
libXau.so.6.0.0         libXft.so               libXTrap.so
libXaw3d.so             libXft.so.2             libXTrap.so.6
libXaw3d.so.7           libXft.so.2.1.2         libXTrap.so.6.4.0
libXaw3d.so.7.0         libXinerama.so          libXt.so

(Continue reading)

headers

Robert Kern | 2 Dec 00:57

Re: Installing ETS-3.0.3 in Sage

On Mon, Dec 1, 2008 at 17:40, Jaap Spies <j.spies@...> wrote:
> Robert Kern wrote:
>> On Mon, Dec 1, 2008 at 17:33, Jaap Spies <j.spies@...> wrote:
>>> Robert Kern wrote:
>>>> On Mon, Dec 1, 2008 at 17:20, Jaap Spies <j.spies@...> wrote:
>>>>
>>>>> sage: from numpy.distutils.system_info import get_info
>>>>>
>>>>> sage: get_info('x11')
>>>>>  {}
>>>> And that's your problem. Where are your X11 libraries and headers?
>>> On the standard place, I suppose. Where else would Fedora keep them?
>>
>> On 64-bit platforms, it keeps the libraries in /usr/lib64/ instead.
>
> Here in 32 bits in /usr/lib:
>
> [jaap <at> paix lib]$ ls libX*
> libX11.so               libXfixes.so.3          libXrender.so.1

> Nothing special I suppose?

Looks right. Show me the result of the following script:

from numpy.distutils.system_info import x11_info
x = x11_info()
print x.get_lib_dirs()
print x.get_include_dirs()
print x.check_libs('/usr/lib', ['X11'], [])
print x.combine_paths('/usr/include', 'X11/X.h')

(Continue reading)

headers

Jaap Spies | 2 Dec 01:02

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:
> On Mon, Dec 1, 2008 at 17:40, Jaap Spies <j.spies@...> wrote:
>> Robert Kern wrote:
>>> On Mon, Dec 1, 2008 at 17:33, Jaap Spies <j.spies@...> wrote:
>>>> Robert Kern wrote:
>>>>> On Mon, Dec 1, 2008 at 17:20, Jaap Spies <j.spies@...> wrote:
>>>>>
>>>>>> sage: from numpy.distutils.system_info import get_info
>>>>>>
>>>>>> sage: get_info('x11')
>>>>>>  {}
>>>>> And that's your problem. Where are your X11 libraries and headers?
>>>> On the standard place, I suppose. Where else would Fedora keep them?
>>> On 64-bit platforms, it keeps the libraries in /usr/lib64/ instead.
>> Here in 32 bits in /usr/lib:
>>
>> [jaap <at> paix lib]$ ls libX*
>> libX11.so               libXfixes.so.3          libXrender.so.1
> 
>> Nothing special I suppose?
> 
> Looks right. Show me the result of the following script:
> 
> from numpy.distutils.system_info import x11_info
> x = x11_info()
> print x.get_lib_dirs()
> print x.get_include_dirs()
> print x.check_libs('/usr/lib', ['X11'], [])
> print x.combine_paths('/usr/include', 'X11/X.h')
>

(Continue reading)

headers

Robert Kern | 2 Dec 01:04

Re: Installing ETS-3.0.3 in Sage

On Mon, Dec 1, 2008 at 18:02, Jaap Spies <j.spies@...> wrote:
> Robert Kern wrote:
>> On Mon, Dec 1, 2008 at 17:40, Jaap Spies <j.spies@...> wrote:
>>> Robert Kern wrote:
>>>> On Mon, Dec 1, 2008 at 17:33, Jaap Spies <j.spies@...> wrote:
>>>>> Robert Kern wrote:
>>>>>> On Mon, Dec 1, 2008 at 17:20, Jaap Spies <j.spies@...> wrote:
>>>>>>
>>>>>>> sage: from numpy.distutils.system_info import get_info
>>>>>>>
>>>>>>> sage: get_info('x11')
>>>>>>>  {}
>>>>>> And that's your problem. Where are your X11 libraries and headers?
>>>>> On the standard place, I suppose. Where else would Fedora keep them?
>>>> On 64-bit platforms, it keeps the libraries in /usr/lib64/ instead.
>>> Here in 32 bits in /usr/lib:
>>>
>>> [jaap <at> paix lib]$ ls libX*
>>> libX11.so               libXfixes.so.3          libXrender.so.1
>>
>>> Nothing special I suppose?
>>
>> Looks right. Show me the result of the following script:
>>
>> from numpy.distutils.system_info import x11_info
>> x = x11_info()
>> print x.get_lib_dirs()
>> print x.get_include_dirs()
>> print x.check_libs('/usr/lib', ['X11'], [])
>> print x.combine_paths('/usr/include', 'X11/X.h')

(Continue reading)

headers

Jaap Spies | 2 Dec 01:14

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:
> On Mon, Dec 1, 2008 at 18:02, Jaap Spies <j.spies@...> wrote:
>> Robert Kern wrote:
>>> On Mon, Dec 1, 2008 at 17:40, Jaap Spies <j.spies@...> wrote:
>>>> Robert Kern wrote:
>>>>> On Mon, Dec 1, 2008 at 17:33, Jaap Spies <j.spies@...> wrote:
>>>>>> Robert Kern wrote:
>>>>>>> On Mon, Dec 1, 2008 at 17:20, Jaap Spies <j.spies@...> wrote:
>>>>>>>
>>>>>>>> sage: from numpy.distutils.system_info import get_info
>>>>>>>>
>>>>>>>> sage: get_info('x11')
>>>>>>>>  {}
>>>>>>> And that's your problem. Where are your X11 libraries and headers?
>>>>>> On the standard place, I suppose. Where else would Fedora keep them?
>>>>> On 64-bit platforms, it keeps the libraries in /usr/lib64/ instead.
>>>> Here in 32 bits in /usr/lib:
>>>>
>>>> [jaap <at> paix lib]$ ls libX*
>>>> libX11.so               libXfixes.so.3          libXrender.so.1
>>>> Nothing special I suppose?
>>> Looks right. Show me the result of the following script:
>>>
>>> from numpy.distutils.system_info import x11_info
>>> x = x11_info()
>>> print x.get_lib_dirs()
>>> print x.get_include_dirs()
>>> print x.check_libs('/usr/lib', ['X11'], [])
>>> print x.combine_paths('/usr/include', 'X11/X.h')
>>>

(Continue reading)

headers

Robert Kern | 2 Dec 01:18

Re: Installing ETS-3.0.3 in Sage

On Mon, Dec 1, 2008 at 18:14, Jaap Spies <j.spies@...> wrote:
> I run the install scipt under the sage env:
>
> AS=as
> LDFLAGS=
...

Hmm, I don't see anything suggestive there. Can you run the following for me?

from numpy.distutils.system_info import x11_info
x = x11_info()
print x.cp.defaults()
print x.cp._sections

--

-- 
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

headers

Robert Kern | 2 Dec 01:20

Re: Installing ETS-3.0.3 in Sage

On Mon, Dec 1, 2008 at 18:18, Robert Kern <robert.kern@...> wrote:
> On Mon, Dec 1, 2008 at 18:14, Jaap Spies <j.spies@...> wrote:
>> I run the install scipt under the sage env:
>>
>> AS=as
>> LDFLAGS=
> ...
>
> Hmm, I don't see anything suggestive there. Can you run the following for me?
>
> from numpy.distutils.system_info import x11_info
> x = x11_info()
> print x.cp.defaults()
> print x.cp._sections

Also

print x.library_extensions()

--

-- 
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

headers

Jaap Spies | 2 Dec 01:28

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:
> On Mon, Dec 1, 2008 at 18:18, Robert Kern <robert.kern@...> wrote:
>> On Mon, Dec 1, 2008 at 18:14, Jaap Spies <j.spies@...> wrote:
>>> I run the install scipt under the sage env:
>>>
>>> AS=as
>>> LDFLAGS=
>> ...
>>
>> Hmm, I don't see anything suggestive there. Can you run the following for me?
>>
>> from numpy.distutils.system_info import x11_info
>> x = x11_info()
>> print x.cp.defaults()
>> print x.cp._sections
> 
> Also
> 
> print x.library_extensions()
> 

[jaap <at> paix sage-3.2.1.rc0]$ ./sage -wthread
----------------------------------------------------------------------
| Sage Version 3.2.1.rc0, Release Date: 2008-11-29                   |
| Type notebook() for the GUI, and license() for information.        |
----------------------------------------------------------------------

sage: from numpy.distutils.system_info import x11_info

sage: x = x11_info()

(Continue reading)

headers

Robert Kern | 2 Dec 01:31

Re: Installing ETS-3.0.3 in Sage

On Mon, Dec 1, 2008 at 18:28, Jaap Spies <j.spies@...> wrote:
> Robert Kern wrote:
>> On Mon, Dec 1, 2008 at 18:18, Robert Kern <robert.kern@...> wrote:
>>> On Mon, Dec 1, 2008 at 18:14, Jaap Spies <j.spies@...> wrote:
>>>> I run the install scipt under the sage env:
>>>>
>>>> AS=as
>>>> LDFLAGS=
>>> ...
>>>
>>> Hmm, I don't see anything suggestive there. Can you run the following for me?
>>>
>>> from numpy.distutils.system_info import x11_info
>>> x = x11_info()
>>> print x.cp.defaults()
>>> print x.cp._sections
>>
>> Also
>>
>> print x.library_extensions()
>>
>
> [jaap <at> paix sage-3.2.1.rc0]$ ./sage -wthread
> ----------------------------------------------------------------------
> | Sage Version 3.2.1.rc0, Release Date: 2008-11-29                   |
> | Type notebook() for the GUI, and license() for information.        |
> ----------------------------------------------------------------------
>
> sage: from numpy.distutils.system_info import x11_info
>

(Continue reading)

headers

Jaap Spies | 2 Dec 01:51

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:
> On Mon, Dec 1, 2008 at 18:28, Jaap Spies <j.spies@...> wrote:
>> Robert Kern wrote:
/lib', 'search_static_first': '0'}
> 
> Okay, that's just odd. Did the Sage packager of numpy modify
> numpy/distutils/system_info.py at all?
> 

I asked around, but with no reslut yet.

> Anyways, the workaround is to make a file ~/.numpy-site.cfg with the contents
> 
> [x11]
> library_dirs=/usr/lib
> include_dirs=/usr/include
> 

Don't know. How will this help installing ets with my install-pkg?
Not only for me, but also for the person who downloads this package?

To be honnest I had no idea that numpy is causing this trouble!

Jaap

headers

Robert Kern | 2 Dec 02:20

Re: Installing ETS-3.0.3 in Sage

On Mon, Dec 1, 2008 at 18:51, Jaap Spies <j.spies@...> wrote:
> Robert Kern wrote:
>> On Mon, Dec 1, 2008 at 18:28, Jaap Spies <j.spies@...> wrote:
>>> Robert Kern wrote:
> /lib', 'search_static_first': '0'}
>>
>> Okay, that's just odd. Did the Sage packager of numpy modify
>> numpy/distutils/system_info.py at all?
>
> I asked around, but with no reslut yet.

I've looked at the numpy-1.2.0.p0.spkg, and there doesn't seem to be
anything suspicious. Is that the version of numpy you have installed?

>> Anyways, the workaround is to make a file ~/.numpy-site.cfg with the contents
>>
>> [x11]
>> library_dirs=/usr/lib
>> include_dirs=/usr/include
>>
>
> Don't know. How will this help installing ets with my install-pkg?

This file will tell numpy.distutils (and consequently Enable's setup
scripts) to look in those locations for the X11 libraries and headers
and ignore the defaults. The defaults appear to be broken in your
installation; I don't know why.

> Not only for me, but also for the person who downloads this package?

(Continue reading)

headers

Jaap Spies | 2 Dec 02:43

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:
> On Mon, Dec 1, 2008 at 18:51, Jaap Spies <j.spies@...> wrote:
>> Robert Kern wrote:
>>> On Mon, Dec 1, 2008 at 18:28, Jaap Spies <j.spies@...> wrote:
>>>> Robert Kern wrote:
>> /lib', 'search_static_first': '0'}
>>> Okay, that's just odd. Did the Sage packager of numpy modify
>>> numpy/distutils/system_info.py at all?
>> I asked around, but with no reslut yet.
> 
> I've looked at the numpy-1.2.0.p0.spkg, and there doesn't seem to be
> anything suspicious. Is that the version of numpy you have installed?
> 

Yes.

>>> Anyways, the workaround is to make a file ~/.numpy-site.cfg with the contents
>>>
>>> [x11]
>>> library_dirs=/usr/lib
>>> include_dirs=/usr/include
>>>
>> Don't know. How will this help installing ets with my install-pkg?
> 
> This file will tell numpy.distutils (and consequently Enable's setup
> scripts) to look in those locations for the X11 libraries and headers
> and ignore the defaults. The defaults appear to be broken in your
> installation; I don't know why.
> 
>> Not only for me, but also for the person who downloads this package?

(Continue reading)

headers

Robert Kern | 2 Dec 03:43

Re: Installing ETS-3.0.3 in Sage

On Mon, Dec 1, 2008 at 19:43, Jaap Spies <j.spies@...> wrote:
> Robert Kern wrote:

>> Let's check a couple of other things. At the shell:
>>
>
> Ok, just before I go to sleep (2.30 AM local time)
>
>> $ locate "*site.cfg"
>
> [jaap <at> paix sage-3.2.1.rc0]$ locate "*site.cfg"

> /home/jaap/work/downloads/sage-3.2.1.rc0/local/lib/python2.5/site-packages/numpy/distutils/site.cfg

Okay, I see the problem. The spkg-install creates this file with a
[DEFAULT] section. This overrides all of the defaults in
system_info.py. Unfortunately, there isn't a terribly convenient way
out of this. numpy's spkg-install could make individual sections for
those it is going to use to build scipy:

[lapack_opt]
library_dirs = ...
include_dirs = ...

[blas_opt]
library_dirs = ...
include_dirs = ...

[fftw]
library_dirs = ...

(Continue reading)

headers

Jaap Spies | 2 Dec 15:42

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:
> On Mon, Dec 1, 2008 at 19:43, Jaap Spies <j.spies@...> wrote:
>> Robert Kern wrote:
> 
>>> Let's check a couple of other things. At the shell:
>>>
>> Ok, just before I go to sleep (2.30 AM local time)
>>
>>> $ locate "*site.cfg"
>> [jaap <at> paix sage-3.2.1.rc0]$ locate "*site.cfg"
> 
>> /home/jaap/work/downloads/sage-3.2.1.rc0/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
> 
> Okay, I see the problem. The spkg-install creates this file with a
> [DEFAULT] section. This overrides all of the defaults in
> system_info.py. Unfortunately, there isn't a terribly convenient way
> out of this. numpy's spkg-install could make individual sections for
> those it is going to use to build scipy:
> 
> [lapack_opt]
> library_dirs = ...
> include_dirs = ...
> 
> [blas_opt]
> library_dirs = ...
> include_dirs = ...
> 
> [fftw]
> library_dirs = ...
> include_dirs = ...

(Continue reading)

headers

Jaap Spies | 2 Dec 16:53

Re: Installing ETS-3.0.3 in Sage

Jaap Spies wrote:

> 
> But in the mean time is there a possibility to get chaco running?
> 

To answer myself: I've got a working chaco by puting the [DEFAULT]
in numpy/distutils/site.cfg aside.

Robert, thanks again!

Jaap

headers

Jaap Spies | 2 Dec 22:31

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:
> On Mon, Dec 1, 2008 at 19:43, Jaap Spies <j.spies@...> wrote:
>> Robert Kern wrote:
> 
>>> Let's check a couple of other things. At the shell:
>>>
>> Ok, just before I go to sleep (2.30 AM local time)
>>
>>> $ locate "*site.cfg"
>> [jaap <at> paix sage-3.2.1.rc0]$ locate "*site.cfg"
> 
>> /home/jaap/work/downloads/sage-3.2.1.rc0/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
> 
> Okay, I see the problem. The spkg-install creates this file with a
> [DEFAULT] section. This overrides all of the defaults in
> system_info.py.

I think this is a real design issue. Why use the crappy numpy distutils to get system info.
I think there are better (more portable) ways to get this info.

Jaap

headers

Gael Varoquaux | 2 Dec 22:33

Re: Installing ETS-3.0.3 in Sage

On Tue, Dec 02, 2008 at 10:31:00PM +0100, Jaap Spies wrote:
> I think this is a real design issue. Why use the crappy numpy distutils to get system info.
> I think there are better (more portable) ways to get this info.

Which one? I'd really like to know, because this is a problem I have seen
everywhere, with all kind of configuration systems. Quite often people
try to fix the problem by themselves by rewritten a configuration system,
and thus introducing different problems.

Gaël

headers

Jaap Spies | 2 Dec 23:49

Re: Installing ETS-3.0.3 in Sage

Gael Varoquaux wrote:
> On Tue, Dec 02, 2008 at 10:31:00PM +0100, Jaap Spies wrote:
>> I think this is a real design issue. Why use the crappy numpy distutils to get system info.
>> I think there are better (more portable) ways to get this info.
> 
> Which one? I'd really like to know, because this is a problem I have seen
> everywhere, with all kind of configuration systems. Quite often people
> try to fix the problem by themselves by rewritten a configuration system,
> and thus introducing different problems.

For now I think I made my point by referring to the failing numpy install.

Alternatives may have there own problems, I agree. There are true believers
in many systems. I don't believe in the approach of Chaco -> Enable -> kiva
using an extern software numpy to get critical system information.

Jaap

> 
> Gaël
> 
> _______________________________________________
> Enthought-dev mailing list
> Enthought-dev@...
> https://mail.enthought.com/mailman/listinfo/enthought-dev
> 
> 
>

headers

Robert Kern | 3 Dec 00:08

Re: Installing ETS-3.0.3 in Sage

On Tue, Dec 2, 2008 at 16:49, Jaap Spies <j.spies@...> wrote:
> Gael Varoquaux wrote:
>> On Tue, Dec 02, 2008 at 10:31:00PM +0100, Jaap Spies wrote:
>>> I think this is a real design issue. Why use the crappy numpy distutils to get system info.
>>> I think there are better (more portable) ways to get this info.
>>
>> Which one? I'd really like to know, because this is a problem I have seen
>> everywhere, with all kind of configuration systems. Quite often people
>> try to fix the problem by themselves by rewritten a configuration system,
>> and thus introducing different problems.
>
> For now I think I made my point by referring to the failing numpy install.

No, you haven't. If you present an alternative that works better, I am
happy to concede the point. Build configuration across many disparate
platforms is simply a hard problem. Demonstrating that one approach
has issues does not mean that there are other approaches which are
free of such issues.

> Alternatives may have there own problems, I agree. There are true believers
> in many systems. I don't believe in the approach of Chaco -> Enable -> kiva
> using an extern software numpy to get critical system information.

<shrug> We're using numpy.distutils to build Enable for several other
reasons (not least that the extension modules use numpy). That
configuration mechanism happened to be there, so we are using it.
Ultimately, it gives the person installing complete control via
~/.numpy-site.cfg, but it does sacrifice some automatic assumptions
that might be made.

(Continue reading)

headers

Jaap Spies | 3 Dec 14:36

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:
> On Tue, Dec 2, 2008 at 16:49, Jaap Spies <j.spies@...> wrote:
[...]
>> For now I think I made my point by referring to the failing numpy install.
> 
> No, you haven't. If you present an alternative that works better, I am
> happy to concede the point. Build configuration across many disparate
> platforms is simply a hard problem. Demonstrating that one approach
> has issues does not mean that there are other approaches which are
> free of such issues.
> 

Ok, you have your point. I was speaking too early (before I studied
the sources!).

[...]
> <shrug> We're using numpy.distutils to build Enable for several other
> reasons (not least that the extension modules use numpy). That
> configuration mechanism happened to be there, so we are using it.
> Ultimately, it gives the person installing complete control via
> ~/.numpy-site.cfg, but it does sacrifice some automatic assumptions
> that might be made.
> 

On second thoughts I think the maintainers of the numpy.spkg are to
blame here by the introduction the [DEFAULT] in the site.cfg.

Thanks for making this clear.

Jaap

(Continue reading)

headers

Chris Casey | 2 Dec 00:47

Re: Installing ETS-3.0.3 in Sage


On Mon, 2008-12-01 at 17:35 -0600, Robert Kern wrote:
> On Mon, Dec 1, 2008 at 17:33, Jaap Spies <j.spies@...> wrote:
> > Robert Kern wrote:
> >> On Mon, Dec 1, 2008 at 17:20, Jaap Spies <j.spies@...> wrote:
> >>
> >>> sage: from numpy.distutils.system_info import get_info
> >>>
> >>> sage: get_info('x11')
> >>>  {}
> >>
> >> And that's your problem. Where are your X11 libraries and headers?
> >
> > On the standard place, I suppose. Where else would Fedora keep them?
> 
> On 64-bit platforms, it keeps the libraries in /usr/lib64/ instead.
> 

I thought it was /usr/X11R6/lib64...?

headers

bryce hendrix | 2 Dec 00:15

Re: Installing ETS-3.0.3 in Sage

Robert Kern wrote:

On Mon, Dec 1, 2008 at 13:41, Jaap Spies <j.spies-8LkvcxCLB6JmR6Xm/wNWPw@public.gmane.org> wrote:
bryce hendrix wrote:
Jaap Spies wrote:
bryce hendrix wrote:

Strangely, distutils used the X11 headers, but didn't bother to link with the X11 library. You might have success setting your LD_FLAGS environment variable, "LD_FLAGS=-lX11", then rebuilding Enable.
Rebuilding with "LD_FLAGS=-lX11" gives the same result :(
That's because the correct environment variable would be spelled LDFLAGS. However, that's not a very good way to let those flags. This is better: $ python setup.py build_ext -lX11 build However, there are probably more flags missing. I'll take a closer look at your build log.

Oops, thanks Robert. I thought that didn't look right. The reason I suggested setting it in the env var versus the command line is Jaap is installing via easy_install.

Bryce

_______________________________________________
Enthought-dev mailing list
Enthought-dev@...
https://mail.enthought.com/mailman/listinfo/enthought-dev