headers
bryce hendrix | 1 Dec 19:26

Re: Installing ETS-3.0.3 in Sage

Jaap Spies wrote:
> Hi,
>
> I gathered some circumstantial evidence:
>
> [jaap <at> paix examples]$ ldd 
> /home/jaap/downloads/sage-3.2.1.rc0/local/lib/python2.5/site-packages/Enable-3.0.2-py2.5-linux-i686.egg/enthought/kiva/agg/_plat_support.so
> 	linux-gate.so.1 =>  (0x00110000)
> 	libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x0011f000)
> 	libm.so.6 => /lib/libm.so.6 (0x00211000)
> 	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0023a000)
> 	libpthread.so.0 => /lib/libpthread.so.0 (0x00248000)
> 	libc.so.6 => /lib/libc.so.6 (0x00289000)
> 	/lib/ld-linux.so.2 (0x0026b000)
> ...
>
> But where it is defined?
>   

Ah, its coming back to me now... The method is part of the Xlib API and 
the real issue here is that _plat_support.so is not linked with it. You 
will probably see some warning in the install log about not being able 
to find the X library, but the build will continue. Do you have 
XFree86-devel installed? If so, please attach the log file in this 
thread (gz it if its too big).

Bryce
Permalink | Reply |
headers
Jaap Spies | 1 Dec 19:51
Favicon

Re: Installing ETS-3.0.3 in Sage

bryce hendrix wrote:
> Jaap Spies wrote:
>> Hi,
>>
>> I gathered some circumstantial evidence:
>>
>> [jaap <at> paix examples]$ ldd 
>> /home/jaap/downloads/sage-3.2.1.rc0/local/lib/python2.5/site-packages/Enable-3.0.2-py2.5-linux-i686.egg/enthought/kiva/agg/_plat_support.so
>> 	linux-gate.so.1 =>  (0x00110000)
>> 	libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x0011f000)
>> 	libm.so.6 => /lib/libm.so.6 (0x00211000)
>> 	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0023a000)
>> 	libpthread.so.0 => /lib/libpthread.so.0 (0x00248000)
>> 	libc.so.6 => /lib/libc.so.6 (0x00289000)
>> 	/lib/ld-linux.so.2 (0x0026b000)
>> ...
>>
>> But where it is defined?
>>   
> 
> Ah, its coming back to me now... The method is part of the Xlib API and 
> the real issue here is that _plat_support.so is not linked with it. You 
> will probably see some warning in the install log about not being able 
> to find the X library, but the build will continue. Do you have 
> XFree86-devel installed? If so, please attach the log file in this 
> thread (gz it if its too big).

No, I don't see any XFree* installed.

The part of the install log regarding enable can be found here:
(Continue reading)

Permalink | Reply |
headers
bryce hendrix | 1 Dec 20:15

Re: Installing ETS-3.0.3 in Sage

Jaap Spies wrote:
bryce hendrix wrote:
Jaap Spies wrote:
Hi, I gathered some circumstantial evidence: [jaap <at> paix examples]$ ldd /home/jaap/downloads/sage-3.2.1.rc0/local/lib/python2.5/site-packages/Enable-3.0.2-py2.5-linux-i686.egg/enthought/kiva/agg/_plat_support.so linux-gate.so.1 => (0x00110000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x0011f000) libm.so.6 => /lib/libm.so.6 (0x00211000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0023a000) libpthread.so.0 => /lib/libpthread.so.0 (0x00248000) libc.so.6 => /lib/libc.so.6 (0x00289000) /lib/ld-linux.so.2 (0x0026b000) ... But where it is defined?
Ah, its coming back to me now... The method is part of the Xlib API and the real issue here is that _plat_support.so is not linked with it. You will probably see some warning in the install log about not being able to find the X library, but the build will continue. Do you have XFree86-devel installed? If so, please attach the log file in this thread (gz it if its too big).
No, I don't see any XFree* installed. The part of the install log regarding enable can be found here: http://sage.math.washington.edu/home/jsp/tests/enable_install.log.gz

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.

Bryce
_______________________________________________
Enthought-dev mailing list
Enthought-dev@...
https://mail.enthought.com/mailman/listinfo/enthought-dev
Permalink | Reply |
headers
Jaap Spies | 1 Dec 20:41
Favicon

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
Permalink | Reply |
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
Permalink | Reply |
headers
Jaap Spies | 2 Dec 00:10
Favicon

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
Permalink | Reply |
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')

--

-- 
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 |
headers
Jaap Spies | 2 Dec 00:20
Favicon

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
----------------------------------------------------------------------
| 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
Permalink | Reply |
headers
Jaap Spies | 2 Dec 00:24
Favicon

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@...
> https://mail.enthought.com/mailman/listinfo/enthought-dev
> 
> 
>
Permalink | Reply |
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
Permalink | Reply |
headers
Jaap Spies | 2 Dec 00:33
Favicon

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.
Permalink | Reply |
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
Permalink | Reply |
headers
Jaap Spies | 2 Dec 00:40
Favicon

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
libXaw7.so              libXinerama.so.1        libXt.so.6
libXaw7.so.7            libXinerama.so.1.0.0    libXt.so.6.0.0
libXaw7.so.7.0.0        libXi.so                libXtst.so
libXaw.so               libXi.so.6              libXtst.so.6
libXaw.so.7             libXi.so.6.0.0          libXtst.so.6.1.0
libXcomposite.so        libXm.so                libXvMC.so
libXcomposite.so.1      libXm.so.2              libXvMC.so.1
libXcomposite.so.1.0.0  libXm.so.2.0.1          libXvMC.so.1.0.0
libXcursor.so           libXmu.so               libXvMCW.so
libXcursor.so.1         libXmu.so.6             libXvMCW.so.1
libXcursor.so.1.0.2     libXmu.so.6.2.0         libXvMCW.so.1.0.0
libXdamage.so           libXmuu.so              libXv.so
libXdamage.so.1         libXmuu.so.1            libXv.so.1
libXdamage.so.1.1.0     libXmuu.so.1.0.0        libXv.so.1.0.0
libXdmcp.so             libXpm.so               libXxf86dga.so
libXdmcp.so.6           libXpm.so.4             libXxf86dga.so.1
libXdmcp.so.6.0.0       libXpm.so.4.11.0        libXxf86dga.so.1.0.0
libXevie.so             libXp.so                libXxf86misc.so
libXevie.so.1           libXp.so.6              libXxf86misc.so.1
libXevie.so.1.0.0       libXp.so.6.2.0          libXxf86misc.so.1.1.0
libXext.so              libXrandr.so            libXxf86vm.so
libXext.so.6            libXrandr.so.2          libXxf86vm.so.1
libXext.so.6.4.0        libXrandr.so.2.1.0      libXxf86vm.so.1.0.0
libXfixes.so            libXrender.so
[jaap <at> paix lib]$

Nothing special I suppose?

Jaap
Permalink | Reply |
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')

--

-- 
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 |
headers
Jaap Spies | 2 Dec 01:02
Favicon

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

sage: from numpy.distutils.system_info import x11_info
sage: x = x11_info()
sage: print x.get_lib_dirs()
['/home/jaap/downloads/sage-3.2.1.rc0/local/lib']
sage: print x.get_include_dirs()
['/home/jaap/downloads/sage-3.2.1.rc0/local/include']
sage: print x.check_libs('/usr/lib', ['X11'], [])
{'libraries': ['X11'], 'library_dirs': ['/usr/lib']}
sage: print x.combine_paths('/usr/include', 'X11/X.h')
['/usr/include/X11/X.h']
sage:

Jaap
Permalink | Reply |
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')
>>
>
> sage: from numpy.distutils.system_info import x11_info
> sage: x = x11_info()
> sage: print x.get_lib_dirs()
> ['/home/jaap/downloads/sage-3.2.1.rc0/local/lib']
> sage: print x.get_include_dirs()
> ['/home/jaap/downloads/sage-3.2.1.rc0/local/include']

And there's the problem. Do you have a site.cfg defined somewhere?
What are your environment variables?

--

-- 
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 |
headers
Jaap Spies | 2 Dec 01:14
Favicon

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')
>>>
>> sage: from numpy.distutils.system_info import x11_info
>> sage: x = x11_info()
>> sage: print x.get_lib_dirs()
>> ['/home/jaap/downloads/sage-3.2.1.rc0/local/lib']
>> sage: print x.get_include_dirs()
>> ['/home/jaap/downloads/sage-3.2.1.rc0/local/include']
> 
> And there's the problem. Do you have a site.cfg defined somewhere?
> What are your environment variables?
> 

I run the install scipt under the sage env:

AS=as
LDFLAGS=
AR=ar
SSH_AGENT_PID=2641
HOSTNAME=paix
RHOME=/home/jaap/downloads/sage-3.2.1.rc0/local/lib/R
UNAME=Linux
TERM=xterm
SHELL=/bin/bash
SAGE_SERVER=http://www.sagemath.org/
SAGE_ORIG_LD_LIBRARY_PATH_SET=True
XDG_SESSION_COOKIE=a70ed397301faa017c5004ce483484d2-1228059172.9449-811211155
HISTSIZE=1000
WISECONFIGDIR=/usr/share/wise2/
SAGE_DATA=/home/jaap/downloads/sage-3.2.1.rc0/data
LIBRARY_PATH=/home/jaap/downloads/sage-3.2.1.rc0/local/lib/
MKDIR=mkdir
GTK_RC_FILES=/etc/gtk/gtkrc:/home/jaap/.gtkrc-1.2-gnome2
WINDOWID=31457864
QTDIR=/usr/lib/qt-3.3
SHAREDFLAGS=-fPIC
QTINC=/usr/lib/qt-3.3/include
GTK_MODULES=gnomebreakpad
DOT_SAGE=/home/jaap/.sage/
USER=jaap
LD_LIBRARY_PATH=/home/jaap/downloads/sage-3.2.1.rc0/local/lib/R/lib:/home/jaap/downloads/sage-3.2.1.rc0/local/lib/openmpi:/home/jaap/downloads/sage-3.2.1.rc0/local/lib/:/usr/lib/xorg
LIBGL_DRIVERS_PATH=/usr/lib/dri
LS_COLORS=no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:do=00;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=01;05;37;41:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.svgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.lzma=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.dz=00;31:*.gz=00;31:*.bz2=00;31:*.tbz2=00;31:*.bz=00;31:*.tz=00;31:*.deb=00;31:*.rpm=00;31:*.jar=00;31:*.rar=00;31:*.ace=00;31:*.zoo=00;31:*.cpio=00;31:*.7z=00;31:*.rz=00;31:*.jpg=00;35:*.jpeg=00;35:*.gif=00;35:*.bmp=00;35:*.pbm=00;35:*.pgm=00;35:*.ppm=00;35:*.tga=00;35:*.xbm=00;35:*.xpm=00;35:*.tif=00;35:*.tiff=00;35:*.png=00;35:*.mng=00;35:*.pcx=00;35:*.mov=00;35:*.mpg=00;35:*.mpeg=00;35:*.m2v=00;35:*.mkv=00;35:*.ogm=00
 ;35:*.mp4=00;35:*.m4v=00;35:*.mp4v=00;35:*.vob=00;35:*.qt=00;35:*.nuv=00;35:*.wmv=00;35:*.asf=00;35:*.rm=00;35:*.rmvb=00;35:*.flc=00;35:*.avi=00;35:*.fli=00;35:*.gl=00;35:*.dl=00;35:*.xcf=00
;35:*.xwd=00;35:*.yuv=00;35:*.svg=00;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:
CUR=/home/jaap/downloads/sage-3.2.1.rc0
SSH_AUTH_SOCK=/tmp/keyring-PrJIPk/ssh
GNOME_KEYRING_SOCKET=/tmp/keyring-PrJIPk/socket
SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/2624,unix/unix:/tmp/.ICE-unix/2624
SAGE_LOCAL=/home/jaap/downloads/sage-3.2.1.rc0/local
SAGE_STARTUP_FILE=/home/jaap/.sage//init.sage
RM=rm
DESKTOP_SESSION=gnome
PATH=/usr/local/sage:/home/jaap/downloads/sage-3.2.1.rc0:/home/jaap/downloads/sage-3.2.1.rc0/local/bin:/usr/local/sage:/usr/local/sage:/usr/lib/qt-3.3/bin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/home/jaap/bin:/usr/local/MuPAD/share/bin:/usr/local/maple9/bin
MAIL=/var/spool/mail/jaap
LD=ld
PWD=/home/jaap/downloads/sage-3.2.1.rc0
INPUTRC=/etc/inputrc
MV=mv
KDE_IS_PRELINKED=1
GNOME_KEYRING_PID=2623
LANG=en_US.UTF-8
__sage__=
GDM_LANG=en_US.UTF-8
KDEDIRS=/usr
SAGE_ROOT=/home/jaap/downloads/sage-3.2.1.rc0
PYTHONHOME=/home/jaap/downloads/sage-3.2.1.rc0/local
SAGE_PACKAGES=/home/jaap/downloads/sage-3.2.1.rc0/spkg
CP=cp
GDMSESSION=gnome
LN=ln
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
CXX=g++
HOME=/home/jaap
SHLVL=5
SDL_AUDIODRIVER=esd
MAKE=make
GNOME_DESKTOP_SESSION_ID=Default
LOGNAME=jaap
PYTHONPATH=:/home/jaap/downloads/sage-3.2.1.rc0/local/lib/python
SAGE_ORIG_LD_LIBRARY_PATH=/usr/lib/xorg
CVS_RSH=ssh
QTLIB=/usr/lib/qt-3.3/lib
GPHELP=/home/jaap/downloads/sage-3.2.1.rc0/local/bin/gphelp
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-lq4GZQEcPM,guid=4b4b8a29bfcf90c88dceda1a4932b225
LESSOPEN=|/usr/bin/lesspipe.sh %s
RANLIB=ranlib
MATPLOTLIBRC=/home/jaap/.sage//
DISPLAY=:0.0
CC=gcc
QT_PLUGIN_PATH=/usr/lib/kde4/plugins
CHMOD=chmod
GP_DATA_DIR=/home/jaap/downloads/sage-3.2.1.rc0/local/share/pari
SAGE_TESTDIR=/home/jaap/downloads/sage-3.2.1.rc0/tmp
TOUCH=touch
G_BROKEN_FILENAMES=1
GPDOCDIR=/home/jaap/downloads/sage-3.2.1.rc0/local/share/pari/doc
SAGE64=no
XAUTHORITY=/var/run/gdm/auth-cookie-XXQ62ULU-for-jaap
COLORTERM=gnome-terminal
_=/usr/bin/env
[jaap <at> paix sage-3.2.1.rc0]$

Jaap
Permalink | Reply |
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
Permalink | Reply |
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
Permalink | Reply |
headers
Jaap Spies | 2 Dec 01:28
Favicon

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

sage: print x.cp.defaults()
{'libraries': '', 'src_dirs': '.:/usr/local/src', 'include_dirs':
'/home/jaap/downloads/sage-3.2.1.rc0/local/include', 'library_dirs': 
'/home/jaap/downloads/sage-3.2.1.rc0/local/lib', 'search_static_first': '0'}

sage: print x.cp._sections
{'x11': {}}

sage: print x.library_extensions()
['.so', '.a']

sage:

Jaap
Permalink | Reply |
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
>
> sage: x = x11_info()
>
> sage: print x.cp.defaults()
> {'libraries': '', 'src_dirs': '.:/usr/local/src', 'include_dirs':
'/home/jaap/downloads/sage-3.2.1.rc0/local/include', 'library_dirs':
> '/home/jaap/downloads/sage-3.2.1.rc0/local/lib', 'search_static_first': '0'}

Okay, that's just odd. Did the Sage packager of numpy modify
numpy/distutils/system_info.py at all?

Anyways, the workaround is to make a file ~/.numpy-site.cfg with the contents

[x11]
library_dirs=/usr/lib
include_dirs=/usr/include

--

-- 
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 |
headers
Jaap Spies | 2 Dec 01:51
Favicon

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
Permalink | Reply |
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?

If Sage's numpy has been altered somehow to not look in the default
locations for X11, then the user will need to provide a
~/.numpy-site.cfg file to tell it.

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

We use numpy.distutils to build the extension modules in Enable. In
particular, we use its configuration system to discover where the X11
libraries are located. There are defaults set in that module that
should have discovered your X11 libraries. I'm not really sure why
they are different.

Let's check a couple of other things. At the shell:

$ locate "*site.cfg"

>From Python:

from numpy.distutils import system_info
print system_info.default_x11_lib_dirs
print system_info.default_x11_include_dirs
print system_info.default_lib_dirs
print system_info.default_include_dirs

--

-- 
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 |
headers
Jaap Spies | 2 Dec 02:43
Favicon

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?
> 
> If Sage's numpy has been altered somehow to not look in the default
> locations for X11, then the user will need to provide a
> ~/.numpy-site.cfg file to tell it.
> 
>> To be honnest I had no idea that numpy is causing this trouble!
> 
> We use numpy.distutils to build the extension modules in Enable. In
> particular, we use its configuration system to discover where the X11
> libraries are located. There are defaults set in that module that
> should have discovered your X11 libraries. I'm not really sure why
> they are different.
> 

Ok, I'm really frustrated that with a standard configuration in
a standard OS (Fedora 9 and Fedora 10) things are so difficult.
I'm not only refering to ETS but also to Jmol, the 3D include for
Sage (I prefer Mayavi2 :)!)

> 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"
/etc/a2ps-site.cfg
/home/jaap/sage-3.0.4.alpha1/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-2.10/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-2.10.3/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-2.10.4/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-2.11/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-2.8.15/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.0/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.0.1/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.0.2/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.0.3/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.0.4/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.0.6/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.1.1/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.1.2/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.1.3/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.1.4/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.2/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.2.1.alpha1/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.2.1.alpha2/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/home/jaap/work/downloads/sage-3.2.1.rc0/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
/usr/local/sage/local/lib/python2.5/site-packages/numpy/distutils/site.cfg
[jaap <at> paix sage-3.2.1.rc0]$

This surprises me somehow :)

> 
>>From Python:
> 
> from numpy.distutils import system_info
> print system_info.default_x11_lib_dirs
> print system_info.default_x11_include_dirs
> print system_info.default_lib_dirs
> print system_info.default_include_dirs
> 

[jaap <at> paix sage-3.2.1.rc0]$ python
Python 2.5.2 (r252:60911, Nov 29 2008, 14:50:32)
[GCC 4.3.0 20080428 (Red Hat 4.3.0-8)] on linux2
Type "help", "copyright", "credits" or "license" for more information.

 >>> from numpy.distutils import system_info
 >>> print system_info.default_x11_lib_dirs
['/usr/X11R6/lib', '/usr/X11/lib', '/usr/lib']
 >>> print system_info.default_x11_include_dirs
['/usr/X11R6/include', '/usr/X11/include', '/usr/include']
 >>> print system_info.default_lib_dirs
['/home/jaap/downloads/sage-3.2.1.rc0/local/lib', '/usr/local/lib', '/usr/lib']
 >>> print system_info.default_include_dirs
['/usr/local/include', '/usr/include', '/home/jaap/downloads/sage-3.2.1.rc0/local/include']
 >>>

Jaap
Permalink | Reply |
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 = ...
include_dirs = ...

This would leave [x11] with the correct defaults in system_info.py.

--

-- 
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 |
headers
Jaap Spies | 2 Dec 15:42
Favicon

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 = ...
> 
> This would leave [x11] with the correct defaults in system_info.py.
> 

Ok, thanks! I'll contact the maintainers of the package.

There will be an update to numpy-1.21 shortly (next week or so).

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

Jaap
Permalink | Reply |
headers
Jaap Spies | 2 Dec 16:53
Favicon

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
Permalink | Reply |
headers
Jaap Spies | 2 Dec 22:31
Favicon

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
Permalink | Reply |
headers
Gael Varoquaux | 2 Dec 22:33
Favicon

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
Permalink | Reply |
headers
Jaap Spies | 2 Dec 23:49
Favicon

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
> 
> 
>
Permalink | Reply |
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.

If you would like to contribute some extra intelligence to the code,
please do so.

--

-- 
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 |
headers
Jaap Spies | 3 Dec 14:36
Favicon

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
Permalink | Reply |
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...?
Permalink | Reply |
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
Permalink | Reply |
headers
Jaap Spies | 1 Dec 20:23
Favicon

Re: Installing ETS-3.0.3 in Sage

bryce hendrix wrote:
> Jaap Spies wrote:
>> bryce hendrix wrote:
>>  
>>> Jaap Spies wrote:
>>>    
>>>> Hi,
>>>>
>>>> I gathered some circumstantial evidence:
>>>>
>>>> [jaap <at> paix examples]$ ldd 
>>>>
/home/jaap/downloads/sage-3.2.1.rc0/local/lib/python2.5/site-packages/Enable-3.0.2-py2.5-linux-i686.egg/enthought/kiva/agg/_plat_support.so 
>>>>
>>>>     linux-gate.so.1 =>  (0x00110000)
>>>>     libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x0011f000)
>>>>     libm.so.6 => /lib/libm.so.6 (0x00211000)
>>>>     libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0023a000)
>>>>     libpthread.so.0 => /lib/libpthread.so.0 (0x00248000)
>>>>     libc.so.6 => /lib/libc.so.6 (0x00289000)
>>>>     /lib/ld-linux.so.2 (0x0026b000)
>>>> ...
>>>>
>>>> But where it is defined?
>>>>         
>>> Ah, its coming back to me now... The method is part of the Xlib API 
>>> and the real issue here is that _plat_support.so is not linked with 
>>> it. You will probably see some warning in the install log about not 
>>> being able to find the X library, but the build will continue. Do you 
>>> have XFree86-devel installed? If so, please attach the log file in 
>>> this thread (gz it if its too big).
>>>     
>>
>> No, I don't see any XFree* installed.
>>
>> The part of the install log regarding enable can be found here:
>> http://sage.math.washington.edu/home/jsp/tests/enable_install.log.gz
>>   
> 
> 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.
> 

I rather see this happen in source because the install-script is run
automatically.

Jaap

> Bryce
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Enthought-dev mailing list
> Enthought-dev@...
> https://mail.enthought.com/mailman/listinfo/enthought-dev
Permalink | Reply |
headers
bryce hendrix | 1 Dec 20:41

Re: Installing ETS-3.0.3 in Sage

Jaap Spies wrote:
bryce hendrix wrote:
Jaap Spies wrote:
bryce hendrix wrote:
Jaap Spies wrote:
Hi, I gathered some circumstantial evidence: [jaap <at> paix examples]$ ldd /home/jaap/downloads/sage-3.2.1.rc0/local/lib/python2.5/site-packages/Enable-3.0.2-py2.5-linux-i686.egg/enthought/kiva/agg/_plat_support.so linux-gate.so.1 => (0x00110000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x0011f000) libm.so.6 => /lib/libm.so.6 (0x00211000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0023a000) libpthread.so.0 => /lib/libpthread.so.0 (0x00248000) libc.so.6 => /lib/libc.so.6 (0x00289000) /lib/ld-linux.so.2 (0x0026b000) ... But where it is defined?
Ah, its coming back to me now... The method is part of the Xlib API and the real issue here is that _plat_support.so is not linked with it. You will probably see some warning in the install log about not being able to find the X library, but the build will continue. Do you have XFree86-devel installed? If so, please attach the log file in this thread (gz it if its too big).
No, I don't see any XFree* installed. The part of the install log regarding enable can be found here: http://sage.math.washington.edu/home/jsp/tests/enable_install.log.gz
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.
I rather see this happen in source because the install-script is run automatically.

I would to, but we need to know if this fixes the problem on your platform :) 
_______________________________________________
Enthought-dev mailing list
Enthought-dev@...
https://mail.enthought.com/mailman/listinfo/enthought-dev
Permalink | Reply |

Gmane