Hi all,
yep, looks like it succeeded ... funny that this would present a problem.
building '_curses' extension
gcc -pthread -fPIC -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -
I/opt/sage-5.12.beta3/local/include -I. -IInclude -I./Include -
I/usr/include/x86_64-linux-gnu -I/usr/local/include -
I/opt/sage-5.12.beta3/spkg/build/python-2.7.5.p1/src/Include -
I/opt/sage-5.12.beta3/spkg/build/python-2.7.5.p1/src -c
/opt/sage-5.12.beta3/spkg/build/python-2.7.5.p1/src/Modules/_cursesmodule.c -o
build/temp.linux-
x86_64-2.7/opt/sage-5.12.beta3/spkg/build/python-2.7.5.p1/src/Modules/_cursesmodule.o
gcc -pthread -shared -L/opt/sage-5.12.beta3/local/lib -
L/opt/sage-5.12.beta3/local/lib build/temp.linux-
x86_64-2.7/opt/sage-5.12.beta3/spkg/build/python-2.7.5.p1/src/Modules/_cursesmodule.o
-L/opt/sage-5.12.beta3/local/lib -L/usr/lib/x86_64-linux-gnu -L/usr/local/lib
-L. -lncurses -lpython2.7 -o build/lib.linux-x86_64-2.7/_curses.so
Cheers,
Martin
On Thursday 22 August 2013 07:40:23 Volker Braun wrote:
> Your Python managed to build the _curses extension? Mine didn't, which is
> presumably why it Python can't get itself confused:
>
> building '_curses' extension
> gcc -pthread -fPIC -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3
> -Wall -I/home/vbraun/opt/
> sage-5.12.beta3/local/include -I. -IInclude -I./Include
> -I/usr/local/include -I/home/vbraun/opt/
> sage-5.12.beta3/spkg/build/python-2.7.5.p1/src/Include
> -I/home/vbraun/opt/sage-5.12.beta3/spkg/b
> uild/python-2.7.5.p1/src -c
> /home/vbraun/opt/sage-5.12.beta3/spkg/build/python-2.7.5.p1/src/Modu
> les/_cursesmodule.c -o
> build/temp.linux-x86_64-2.7/home/vbraun/opt/sage-5.12.beta3/spkg/build/py
> thon-2.7.5.p1/src/Modules/_cursesmodule.o
> gcc -pthread -shared -L/home/vbraun/opt/sage-5.12.beta3/local/lib
> -L/home/vbraun/opt/sage-5.12.b
> eta3/local/lib
> build/temp.linux-x86_64-2.7/home/vbraun/opt/sage-5.12.beta3/spkg/build/pytho
> n-2.7 .5.p1/src/Modules/_cursesmodule.o
> -L/home/vbraun/opt/sage-5.12.beta3/local/lib -L/usr/local/lib
> -L. -lncursesw -lpython2.7 -o build/lib.linux-x86_64-2.7/_curses.so
> *** WARNING: renaming "_curses" since importing it failed:
> /lib64/libncursesw.so.5: undefined sy
> mbol: _nc_putchar
> building '_curses_panel' extension
> gcc -pthread -fPIC -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3
> -Wall -I/home/vbraun/opt/
> sage-5.12.beta3/local/include -I. -IInclude -I./Include
> -I/usr/local/include -I/home/vbraun/opt/
> sage-5.12.beta3/spkg/build/python-2.7.5.p1/src/Include
> -I/home/vbraun/opt/sage-5.12.beta3/spkg/b
> uild/python-2.7.5.p1/src -c
> /home/vbraun/opt/sage-5.12.beta3/spkg/build/python-2.7.5.p1/src/Modu
> les/_curses_panel.c -o
> build/temp.linux-x86_64-2.7/home/vbraun/opt/sage-5.12.beta3/spkg/build/py
> thon-2.7.5.p1/src/Modules/_curses_panel.o
> gcc -pthread -shared -L/home/vbraun/opt/sage-5.12.beta3/local/lib
> -L/home/vbraun/opt/sage-5.12.beta3/local/lib
> build/temp.linux-x86_64-2.7/home/vbraun/opt/sage-5.12.beta3/spkg/build/pytho
> n-2.7.5.p1/src/Modules/_curses_panel.o
> -L/home/vbraun/opt/sage-5.12.beta3/local/lib -L/usr/local/lib -L. -lpanelw
> -lncursesw -lpython2.7 -o build/lib.linux-x86_64-2.7/_curses_panel.so ***
> WARNING: renaming "_curses_panel" since importing it failed:
> /lib64/libncursesw.so.5: undefined symbol: _nc_putchar
>
> On Thursday, August 22, 2013 2:22:50 PM UTC+1, Martin Albrecht wrote:
> > Hi all,
> >
> > I am running Linux here. I found that link as well and played with my TERM
> > settings, but nothing is working so far:
> >
> > sage: osos.environ["TERM"]
> > 'xterm-new'
> > sage: ZZ?
> > WARNING: terminal is not fully functional
> > - (press RETURN)
> >
> > ... and then I am back in the 90s with "more".
> >
> > Cheers,
> > Martin
> >
> > On Thursday 22 August 2013 06:12:29 Volker Braun wrote:
> > > The change is because we switched to ncurses instead of termcap.
> > >
> > > Are you on OSX? Your TERM should be set to xterm-new or, even
> > > better, xterm-256color
> > >
> > > https://code.google.com/p/iterm2/issues/detail?id=1956
> > >
> > > On Thursday, August 22, 2013 1:56:09 PM UTC+1, Martin Albrecht wrote:
> > > > Hi all,
> > > >
> > > > with Sage 5.12.beta3 I get:
> > > >
> > > > sage: os.environ["TERM"]
> > > > 'xterm'
> > > > sage: ZZ?
> > > >
> > > > /opt/sage-5.12/local/lib/python/curses/__init__.pyc in initscr()
> > > >
> > > > 31 # instead of calling exit() in error cases.
> > > > 32 setupterm(term=_os.environ.get("TERM", "unknown"),
> > > >
> > > > ---> 33 fd=_sys.__stdout__.fileno())
> > > >
> > > > 34 stdscr = _curses.initscr()
> > > >
> > > > 35 for key, value in _curses.__dict__.items():
> > > > error: setupterm: could not find terminal
> > > > sage:
> > > >
> > > > This is in konsole (KDE's console). Any ideas?
> > > >
> > > > Cheers,
> > > > Martin
--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6532AFB4
_otr: 47F43D1A 5D68C36F
