#12131: $SAGE_LOCAL/lib and lib64
--------------------------+-------------------------------------------------
   Reporter:  vbraun      |          Owner:  GeorgSWeber             
       Type:  defect      |         Status:  new                     
   Priority:  blocker     |      Milestone:  sage-5.0                
  Component:  build       |       Keywords:                          
Work_issues:              |       Upstream:  N/A                     
   Reviewer:  Simon King  |         Author:  Volker Braun, Simon King
     Merged:              |   Dependencies:  #12057                  
--------------------------+-------------------------------------------------
Changes (by newvalueoldvalue):

  * reviewer:  => Simon King
  * author:  => Volker Braun, Simon King


Old description:

> Some distributions set up autotools to install libraries into
> `%{prefix}/lib64`, which breaks Sage's assumption that libraries are
> installed in `$SAGE_LOCAL/lib`. In particular, !OpenSuse64 according to
> this thread https://groups.google.com/d/topic/sage-devel/LS-
> u8E77NJQ/discussion
>
> It seems like we have two options:
>   * Always call `./configure --libdir='${prefix}/lib'` to explicitly
> specify the library directory, or
>   * Set up a symlink `$SAGE_LOCAL/lib64` -> `$SAGE_LOCAL/lib`.
>
> The symlink is the lazy thing to do but will probably break again with
> the next architectural change. Fixing the configure call seems the right
> thing to do but will need some work to patch up all spkgs.
>
> Updated spkgs:
>   * http://www.stp.dias.ie/~vbraun/Sage/spkg/readline-6.2.p2.spkg

New description:

 Some distributions set up autotools to install libraries into
 `%{prefix}/lib64`, which breaks Sage's assumption that libraries are
 installed in `$SAGE_LOCAL/lib`. In particular, !OpenSuse64 according to
 this thread https://groups.google.com/d/topic/sage-devel/LS-
 u8E77NJQ/discussion

 It seems like we have two options:
   * Always call `./configure --libdir='${prefix}/lib'` to explicitly
 specify the library directory, or
   * Set up a symlink `$SAGE_LOCAL/lib64` -> `$SAGE_LOCAL/lib`.

 The symlink is the lazy thing to do but will probably break again with the
 next architectural change. Fixing the configure call seems the right thing
 to do but will need some work to patch up all spkgs.

 Updated spkgs:

   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/boehm_gc-7.2.alpha6.p2.spkg
   * http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE
 /cddlib-094f.p9.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/ecl-11.1.2.cvs20111120.p1.spkg
   *
 http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/ecm-6.3.p3.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/freetype-2.3.5.p4.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/gd-2.0.35.p6.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/givaro-3.2.13rc2.p3.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/glpk-4.44.p0.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/gnutls-2.2.1.p6.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/gsl-1.15.p0.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/iml-1.0.1.p14.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/libfplll-3.0.12.p2.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/libgcrypt-1.4.4.p4.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/libgpg_error-1.6.p4.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/libm4ri-20111004.p0.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/libm4rie-20111004.p0.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/libpng-1.2.35.p4.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/linbox-1.1.6.p6.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/maxima-5.23.2.p3.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/mpir-2.1.3.p8.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/mpfi-1.3.4-cvs20071125.p9.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/mpfr-2.4.2.p0.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/opencdk-0.6.6.p6.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/ppl-0.11.2.p0.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/pynac-0.2.3.p0.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/python-2.6.4.p13.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/r-2.14.0.p1.spkg
   * http://www.stp.dias.ie/~vbraun/Sage/spkg/readline-6.2.p2.spkg
   *
 
http://http://sage.math.washington.edu/home/SimonKing/SAGE/SUSE/sqlite-3.7.5.p0.spkg

 Note that I based the r-package on the version from #12057 (which has
 already been fixed).

--

Comment:

 With the new package versions that I have posted on my sage.math account
 (see ticket description), `local/lib64/` remains empty, and more
 importantly all long tests pass.

 I noticed that #12139 is now fixed. Therefore I will provide a new mpir
 version based on that. So, not "needs review" yet...

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