#11447: python spkg build fails on Ubuntu 11.04 derivative Mint 11
-----------------------------------------+----------------------------------
   Reporter:  pipedream                  |          Owner:  pipedream     
       Type:  defect                     |         Status:  needs_work    
   Priority:  major                      |      Milestone:  sage-4.7.1    
  Component:  build                      |       Keywords:                
Work_issues:                             |       Upstream:  N/A           
   Reviewer:  David Kirkby, Bill Odefey  |         Author:  Jan Groenewald
     Merged:                             |   Dependencies:                
-----------------------------------------+----------------------------------

Comment(by medlock):

 Replying to [comment:14 medlock]:
 > Replying to [comment:13 medlock]:
 > > ...
 > > The solution that's in Python 2.7 and in Debian's patches to Python
 2.6 (patch deb-setup.diff attached) is to use {{{dpkg-architecture
 -qDEB_HOST_MULTIARCH}}}.  These packages use this command to set the
 library paths correctly.
 > >
 > > This requires that the optional package dpkg-dev is installed.  A
 wrapper should probably be written that complains if {{{lsb_release -i}}}
 is (Debian|Ubuntu|Mint) and {{{dpkg-architecture}}} is not present,
 otherwise the build will fail without the user knowing why...
 >
 > All this can get ripped out when Sage upgrades to Python 2.7, where this
 issue is fixed...

 See also [http://lists.debian.org/debian-devel/2011/06/msg00431.html].

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11447#comment:15>
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