#7761: Python 2.6.2.p4 faills to build on Open Solaris
------------------------------------------------------------+---------------
   Reporter:  drkirkby                                      |       Owner:  
drkirkby           
       Type:  defect                                        |      Status:  new 
               
   Priority:  major                                         |   Milestone:  
sage-4.3.1         
  Component:  solaris                                       |    Keywords:  
python open solaris
Work_issues:                                                |      Author:      
               
   Upstream:  None of the above - read trac for reasoning.  |    Reviewer:      
               
     Merged:                                                |  
------------------------------------------------------------+---------------
 I believe William is aware of this bug and said it can be fixed by
 installing OpenSSL or similar. But I am unable to find a trac ticket for
 it, so I thought I'd open one. It's interesting this issue does not arise
 on Solaris 10 (SPARC), despite OpenSSL libraries not being present there
 either. This bug seems to come up a lot on linux too, as a Google search
 shows.

 On a Sun Ultra 27 (Intel Xeon processor), running Open Solaris 06/2009, I
 get the following problem when python is being built.

 {{{
 copying build/scripts-2.6/pydoc ->
 /export/home/drkirkby/sage-4.3.rc2/local/bin
 changing mode of /export/home/drkirkby/sage-4.3.rc2/local/bin/2to3 to 755
 changing mode of /export/home/drkirkby/sage-4.3.rc2/local/bin/smtpd.py to
 755
 changing mode of /export/home/drkirkby/sage-4.3.rc2/local/bin/idle to 755
 changing mode of /export/home/drkirkby/sage-4.3.rc2/local/bin/pydoc to 755
 running install_egg_info
 Removing /export/home/drkirkby/sage-4.3.rc2/local/lib/python2.6/lib-
 dynload/Python-2.6.2-py2.6.egg-info
 Writing /export/home/drkirkby/sage-4.3.rc2/local/lib/python2.6/lib-
 dynload/Python-2.6.2-py2.6.egg-info
 if test -f /export/home/drkirkby/sage-4.3.rc2/local/bin/python -o -h
 /export/home/drkirkby/sage-4.3.rc2/local/bin/python; \
         then rm -f /export/home/drkirkby/sage-4.3.rc2/local/bin/python; \
         else true; \
         fi
 (cd /export/home/drkirkby/sage-4.3.rc2/local/bin; ln python2.6 python)
 rm -f /export/home/drkirkby/sage-4.3.rc2/local/bin/python-config
 (cd /export/home/drkirkby/sage-4.3.rc2/local/bin; ln -s python2.6-config
 python-config)
 /usr/bin/ginstall -c -m 644 ./Misc/python.man \
 /export/home/drkirkby/sage-4.3.rc2/local/share/man/man1/python.1
 make[2]: Leaving directory
 `/export/home/drkirkby/sage-4.3.rc2/spkg/build/python-2.6.2.p4/src'
 Sleeping for three seconds before testing python
 Traceback (most recent call last):
   File "<string>", line 1, in <module>
   File "/export/home/drkirkby/sage-4.3.rc2/local/lib/python/hashlib.py",
 line 136, in <module>
     md5 = __get_builtin_constructor('md5')
   File "/export/home/drkirkby/sage-4.3.rc2/local/lib/python/hashlib.py",
 line 63, in __get_builtin_constructor
     import _md5
 ImportError: No module named _md5

 real    1m38.244s
 user    1m15.115s
 sys     0m13.132s
 sage: An error occurred while installing python-2.6.2.p4

 }}}

 I'm not sure if this should be reported upstream or not. Some feedback on
 that might be useful. If so, I will report it to a python bug tracker or
 similar. The issue seems to arrise often enough.

 Dave

 PS, to even get to this point, I had to delete the following list of
 files, to get around a gnutls issue in #7387.

 {{{
     * SAGE_LOCAL/include/gcrypt-module.h
     * SAGE_LOCAL/include/gpg-error.h
     * SAGE_LOCAL/include/gcrypt.h
     * SAGE_LOCAL/lib/libgcrypt*
     * SAGE_LOCAL/lib/libgpg*
 }}}

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7761>
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