#8048: command to gather build report on a platform/hardware combination
---------------------------+------------------------------------------------
   Reporter:  mvngu        |       Owner:  tbd       
       Type:  enhancement  |      Status:  new       
   Priority:  major        |   Milestone:  sage-4.5.2
  Component:  misc         |    Keywords:            
     Author:               |    Upstream:  N/A       
   Reviewer:               |      Merged:            
Work_issues:               |  
---------------------------+------------------------------------------------

Comment(by drkirkby):

 Replying to [comment:17 jasonbhill]:
 > I attached a new file. I made the 'useless cat' and other changes.
 (Thanks Dave!)

 You are welcome.

 > Some more notes:
 >
 >  * cpu throttling: It is easy to determine if a cpu supports throttling,
 but can be a pain to determine (across various linux distributions) if it
 is enabled. Even from Ubuntu 9.10 to 10.04, this changed, and both are
 inconsistent with the Debian installations I've tried. So, I'm not
 incredibly optimistic here.

 You do not surprise me. I came to the same conclusion on Solaris too.

 >  * Getting the sage banner isn't a problem, so long as I know my pwd and
 how that relates to the banner's location. I haven't yet assumed that this
 script is executed anywhere specific.
 >  * I changed the gcc version command to output the entire output. The
 extra lines now included are only copyright info though, and so I'd
 question if we'd want them.

 We should be able to get all the parameters that gcc was configured with

 {{{
 drkir...@hawk:~$ gcc -v
 Using built-in specs.
 Target: i386-pc-solaris2.11
 Configured with: /export/home/drkirkby/gcc-4.4.4/configure
 --prefix=/usr/local/gcc-4.4.4-multilib --enable-languages=c,c++,fortran
 --with-gmp=/usr/local/gcc-4.4.4-multilib --with-
 mpfr=/usr/local/gcc-4.4.4-multilib --disable-nls --enable-checking=release
 --enable-werror=no --enable-multilib --with-system-zlib --enable-bootstrap
 --with-gnu-as --with-as=/usr/local/binutils-2.20/bin/as --without-gnu-ld
 --with-ld=/usr/ccs/bin/ld
 Thread model: posix
 gcc version 4.4.4 (GCC)
 }}}

 that lot can be very useful to know.

 >  * I'll add the netstat command (and/or equivalent).

 OK.

 >  * diskspace is relatively easy. I'll add that as well.

 How do you propose to get the disk space? I came to the conclusion that
 was quite difficult, and have not found a way.

 > It looks like the OS-X commands are somewhat straightforward, and the
 hardware is much more standardized there. Dave: We have a couple of lists
 of relevant Sunos commands... can we develop a single list of what is
 useful and what isn't? I have Open Solaris on a machine and so testing
 won't be an issue.


 Yes. It's late here. I will get onto that after some sleep.

 Dave

 > John:
 >
 >  * You want to update some of the skynet information you posted before.
 The cpu information for at least one of the machines changed (since I
 thought 'uniq' would apply 'sort' and it doesn't... meaning that the cores
 /cpu-count is off).
 >  * I also added the correct greps to attempt to get information from
 those Itaniums. My best guess as to why those topology numbers are so
 strange is that those machines may actually accept 4 processors, but only
 have 2 plugged in.

 It might be worth giving memconf a try, to see what it finds. I'm not
 suggesting including that, but it might confirm your guesses.

 If that's not the case, then it's buggy and there just aren't enough
 people using those cpus to make it worth fixing.

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