#9201: Add missing R modules and make `spkg-check` pass on Solaris
-----------------------+----------------------------------------------------
   Reporter:  mpatel   |       Owner:  drkirkby
       Type:  defect   |      Status:  new     
   Priority:  major    |   Milestone:          
  Component:  solaris  |    Keywords:          
     Author:           |    Upstream:  N/A     
   Reviewer:           |      Merged:          
Work_issues:           |  
-----------------------+----------------------------------------------------

Comment(by drkirkby):

 Replying to [comment:2 kcrisman]:
 > Thanks for this important report.  I am not sure why these are not
 building, because all of these modules are 'Recommended' which we recently
 re-enabled (and do exist elsewhere, as you noted).  My guess is that these
 other packages did not build because they rely on Matrix and it didn't
 build.
 >
 > It's not quite clear to me where these doctests would go.  The R
 interface docs are supposed to test that the interface works, not that R
 itself built properly.  The easiest way to test these is simply
 > {{{
 > r.library('package_name')
 > }}}

 I've no idea where the tests would go, or how to write them. But IMHO, if
 parts of R are non-functional (and it seems to be several parts), this
 should be detected. We test that some python modules have built,
 especially those that have known to be problematic, like _hashlib.

 I'm still puzzled why R can't find libgcc_s.so.1, as it is definately
 there. running
 {{{
 $ sage -sh
 $ cd local/lib
 $ ldd * | grep libgcc_s.so.1
 }}}
 I can see numerous parts of Sage link to libgcc_so.1. In fact, there are
 127 of them! Here's the first one (certtool), if I run 'ldd' to see what
 it is linked against

 {{{
 certtool:
         libgnutls.so.26 =>
 /export/home/drkirkby/32/sage-4.4.3/local/lib//libgnutls.so.26
         libz.so =>
 /export/home/drkirkby/32/sage-4.4.3/local/lib//libz.so
         libgcrypt.so.11 =>
 /export/home/drkirkby/32/sage-4.4.3/local/lib//libgcrypt.so.11
         libgpg-error.so.0 =>
 /export/home/drkirkby/32/sage-4.4.3/local/lib//libgpg-error.so.0
         libreadline.so.6 =>
 /export/home/drkirkby/32/sage-4.4.3/local/lib//libreadline.so.6
         libnsl.so.1 =>   /lib/libnsl.so.1
         libsocket.so.1 =>        /lib/libsocket.so.1
         libc.so.1 =>     /lib/libc.so.1
         libgcc_s.so.1 =>         /usr/local/gcc-4.4.3/lib/libgcc_s.so.1
         libmp.so.2 =>    /lib/libmp.so.2
         libmd5.so.1 =>   /lib/libmd5.so.1
         libscf.so.1 =>   /lib/libscf.so.1
         libdoor.so.1 =>  /lib/libdoor.so.1
         libuutil.so.1 =>         /lib/libuutil.so.1
         libm.so.2 =>     /lib/libm.so.2
         /platform/SUNW,Sun-Blade-1000/lib/libc_psr.so.1
         /platform/SUNW,Sun-Blade-1000/lib/libmd5_psr.so.1
 }}}

 certool runs too.

 {{{
 sage subshell$ ./certtool
 Certtool help
 Usage: certtool [options]
      -s, --generate-self-signed
                               Generate a self-signed certificate.
      -c, --generate-certificate
                               Generate a signed certificate.
      --generate-proxy         Generate a proxy certificate.
 }}}

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