#10226: Rewrite ATLAS spkg-install
----------------------------+-----------------------------------------------
   Reporter:  vbraun        |       Owner:  GeorgSWeber
       Type:  enhancement   |      Status:  needs_work 
   Priority:  major         |   Milestone:             
  Component:  build         |    Keywords:  ATLAS      
     Author:  Volker Braun  |    Upstream:  N/A        
   Reviewer:                |      Merged:             
Work_issues:                |  
----------------------------+-----------------------------------------------

Comment(by drkirkby):

 Replying to [comment:7 vbraun]:
 > ATLAS 3.8.3 is the latest stable release. The next release should come
 soon but until its out we should stick with 3.8.3

 Normally I would agree with you, but Clint, who is the ATLAS developer,
 has advised us '''not''' to use the latest stable release, but instead use
 the development release. He has also said off list that he will not be
 making many changes to ATLAS due to other commitments. The Sage on gentoo
 project is using the latest ATLAS without issue

 https://groups.google.com/group/sage-
 
devel/browse_thread/thread/f3fa4f8737437d7f/5528028cc0c16975?lnk=gst&q=atlas&hl=en#5528028cc0c16975


 > ATLAS is also very difficult to build and it would be a nightmare to
 rewrite the spkg-install in POSIX shell script.

 As it is now, I agree. But there's an awful lot of junk in there. It is a
 non-trivial task, but really we should update ATLAS.

 > This is why I rewrote the mixture of shell script, Perl, and Python in
 pure Python.


 Yes, but it seriously increases the time to to build Sage, as numerous
 packages have to be build before Python is built, but if

  * The small bit of Python in ATLAS is removed
  * The small bit of Python in the Fortran package is removed

 then it will be possible to start the build of ATLAS much earlier.
 Currently, builds are often building ATLAS for a long time, with nothing
 else going on.

 >
 > I also take it from jhpalmieri's comment that "ld -V" exits with a non-
 zero exit code on t2 (where I don't have an account). I'll add a
 workaround later...

 I can create you an account on {{{t2.math}}}.

 To answer John's point, no the passwords are not shared with t2, as the
 Linux based NIS is not working happily with the Sun NIS. It is possible to
 get around, but it is a non-trivial task. William asked someone to set it
 up, without mentioning this to me. The guy left the machine unusable. The
 only way was to log in on the console. I sorted that out, but have never
 looked at the NIS issues.

 Apparenlty the latest ATLAS builds in under an hour on t2.math, compared
 to the 7 hours it takes now. But I think that is only as a 64-bit
 application, as I don't  think ATLAS has the 32-bit tuning parameters for
 t2.math. But I think sorting that out will be somewhat easier than with
 the current ATLAS, as the new ATLAS has the code to detect the T2+
 processors on t2.math.
 Dave

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