#6990: [with spkg, needs review] readline tab completion has an extra space
appended
----------------------+-----------------------------------------------------
 Reporter:  jason     |       Owner:  mabshoff  
     Type:  defect    |      Status:  new       
 Priority:  blocker   |   Milestone:  sage-4.1.2
Component:  packages  |    Keywords:            
 Reviewer:            |      Author:            
   Merged:            |  
----------------------+-----------------------------------------------------

Comment(by ddrake):

 I'm trying to build 4.1.2.alpha4 on Arch amd64, and with the new
 readline/python package, I'm getting "undefined symbols". It compiles
 readline just fine, and then it starts working on the sqlite spkg, and
 immediately bombs out with:
 {{{
 /bin/bash: symbol lookup error: $SAGE_ROOT/local/lib/libreadline.so.6:
 undefined symbol: PC
 }}}
 I tried skipped sqlite (by touching spkg/installed/sqlite-3.6.17) and when
 it started working on libgpg_error, it immediately failed with the same
 error.

 It looks like the shell is getting confused and picking up the wrong
 libreadline, probably because Arch includes readline 6. On other systems,
 maybe this isn't a problem because the shell looks for a different
 readline...I guess?

 On Ubuntu Karmic (9.10) amd64, I don't see this error, even though it does
 use readline 6.

 (Apologies if this comment should be on the readline spkg ticket, or
 should be in a new ticket...)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6990#comment:10>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to