#10051: Building ATLAS fails at STAGE 2-1-2: CacheEdge DETECTION
--------------------+-------------------------------------------------------
 Reporter:  tux21b  |         Owner:  GeorgSWeber
     Type:  defect  |        Status:  new        
 Priority:  major   |     Milestone:             
Component:  build   |    Resolution:             
 Keywords:          |        Author:             
 Upstream:  N/A     |      Reviewer:             
   Merged:          |   Work_issues:             
--------------------+-------------------------------------------------------
Changes (by drkirkby):

  * status:  closed => new
  * resolution:  worksforme =>


Comment:

 Replying to [comment:3 tux21b]:
 > so I am quite sure that something was changed in Sage 4.6 which solves
 my problem.
 >
 > Many thanks for that!
 >
 > Regards,[[BR]]
 > Christoph

 The changelog in SPKG.txt for ATLAS tells you what has changed.

 {{{
 == ChangeLog ==

 == atlas-3.8.3.p16 (John Palmieri, September 19th 2010) ==
  * Make spkg-check work when using SAGE_ATLAS_LIB: if SAGE_ATLAS_LIB
    is set, skip the self-tests.

 == atlas-3.8.3.p15 (David Kirkby, September 6th 2010) ==
  * Make SAGE_ATLAS_LIB use static libraries on all platforms,
    as building two shared libraries often fails on Linux, and
    messes things up on Solaris. The static library is less hassle
    all around. Worth noting is that the ATLAS package only builds
    the static library and Wolfram Research only ship the static
    library with Mathematica, despite they usually use shared
    libraries. To ensure full compatibility with a fresh build
    of ATLAS, the symbolic links are created for the shared libraries too.
    The links will fail to be created if the shared libraries do not exist,
    but will not cause any extra problems.
  * Update the list of dependencies to include Python and Lapack (see
    spkg/deps)
  * Note that the ATLAS build process could be made much quicker if its
    depenancy on Python was removed. Since the amount of Python code is
    very small compared to the bash code, this seems logical to do at
    a later date. The Fortran package would need the same change - but
 again
    the amount of Python in that is trivial.
  * Add a note that make-correct-shared.sh is badly named, as it often
 fails.
  * Remove the OS X specific code from make-correct-shared.sh, as ATLAS is
    never installed on OS X - see the spkg-install-script.

 == atlas-3.8.3.p14 (David Kirkby, August 10th 2010) ==
 }}}

 atlas-3.8.3.p15 should link both the shared and static libraries. If it is
 not, then we have a bug.


 If you do not use SAGE_ATLAS_LIB, I cant think of anything that should
 have changed. that would have affected your CacheEdge DETECTION problem. I
 think its just more luck than anything else.

 This probably depends on system load. The actual building of ATLAS has
 remiained unchanged for ages - only the libraries have been altered, but
 the CacheEdge DETECTION fails well before any library issues are touched.

 Only the release manager should generally close tickets, though those with
 admin priviledge do so occasionally when it is very clear an issue needs
 closing. In this case, you should not have closed it.

 This issues does not tend to be totally reproducible, and I think there is
 a real problem here.

 Dave

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