Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Chris Samuel
On Wednesday 25 April 2012 19:38:00 Brice Goglin wrote: > How do people feel about this? It sounds like what you have is a conflict between the policies of Debian (and hence Ubuntu) and the expectations of RHEL/CentOS users. Debian Policy is fairly clear on this matter: # 11.8.1 Providing X s

Re: [hwloc-devel] Strange difference

2010-03-30 Thread Chris Samuel
Be interesting to see what it would look like on a large SGI UV, for instance.. -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC This email may come with a PGP signature as a file. Do not panic. For more info see: http://en.wikipedia.org/wiki/OpenPGP signature.asc Description: Th

Re: [hwloc-devel] Strange difference

2010-03-30 Thread Chris Samuel
(so far) describing things is in terms of sockets and cores. Wouldn't be surprised if someone pointed out an ambiguity in those too! cheers, Chris -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC This email may come with a PGP signature as a file. Do not panic. For more in

Re: [hwloc-devel] "compar"

2009-12-21 Thread Chris Samuel
- "Jeff Squyres" wrote: > I'll add the "e". Thanks for avoiding the Thompson effect.. ;-) # Ken Thompson was once asked what he would do # differently if he were redesigning the UNIX # system. His reply: "I'd spell creat with an e." cheers! Chris -- Christopher Samuel - (03) 9925 4751

Re: [hwloc-devel] 0.9.3rc2 out

2009-12-01 Thread Chris Samuel
- "Jeff Squyres" wrote: > A lot of these are "unreferenced parameters" which > I think we should clean up someday, but not today. ;-) Fair comment. ;-) > The stdc99/stgnu99 one is worth looking at -- probably not for this > release, but it does seem like we should straighten it out. Th

Re: [hwloc-devel] Crash with ignoring HWLOC_OBJ_NODE in 0.9.2

2009-11-30 Thread Chris Samuel
- "Samuel Thibault" wrote: > What do you mean by "module support"? http://modules.sourceforge.net/ They make managing multiple software installations on clusters much much easier.. -- Christopher Samuel - (03) 9925 4751 - Systems Manager The Victorian Partnership for Advanced Computing

Re: [hwloc-devel] 0.9.3rc2 out

2009-11-25 Thread Chris Samuel
- "Jeff Squyres" wrote: > Please beat it up! Compiles fine with PGI 10.0 and GCC 4.4.2, but we are getting warnings with Intel 11.1 for all files saying: icc: command line warning #10121: overriding '-stdc99' with '-stdgnu99' icc: com

Re: [hwloc-devel] Crash with ignoring HWLOC_OBJ_NODE in 0.9.2

2009-11-21 Thread Chris Samuel
Hi Michael, - "Michael Raymond" wrote: > Our architecture has blades with two Nehalems on > them, and the blades are connected together in a > CC-NUMA fashion. I've heard on the grapevine that there will be memory only blades too, which will have a Nehalem EX on them but with all cores disa

Re: [hwloc-devel] Pgcc issues fixed?

2009-11-04 Thread Chris Samuel
- "Chris Samuel" wrote: > - "Jeff Squyres" wrote: > > > K. Clear for a final rc / release? > > Go for it, am just about to go run a training course > now so won't be available until this arvo Melbourne > time.. Seems fine with PGI, I

Re: [hwloc-devel] Pgcc issues fixed?

2009-11-04 Thread Chris Samuel
- "Jeff Squyres" wrote: > K. Clear for a final rc / release? Go for it, am just about to go run a training course now so won't be available until this arvo Melbourne time.. cheers! Chris -- Christopher Samuel - (03) 9925 4751 - Systems Manager The Victorian Partnership for Advanced Comp

Re: [hwloc-devel] Pgcc issues fixed?

2009-11-04 Thread Chris Samuel
- "Jeff Squyres" wrote: > Thanks for your patience! Samuel just committed a > bunch more -- try the next one: That fixed up the PGI warnings, but I'm still seeing a heap with the Intel compilers. Output attached again. [csamuel@tango hwloc-0.9.1rc4r1282]$ icc -V Intel(R) C Intel(R) 64 C

Re: [hwloc-devel] Pgcc issues fixed?

2009-11-03 Thread Chris Samuel
- "Chris Samuel" wrote: > Will try PGI 7.0 now. I can confirm it compiles OK with PGI 7.0, 7.1 and 7.2 with the same warnings as for 8.0. These warnings also appear with 9.0. Lots of warnings from the Intel v11 compilers, I've attached a text file for the entire make p

Re: [hwloc-devel] Pgcc issues fixed?

2009-11-03 Thread Chris Samuel
- "Chris Samuel" wrote: > Grabbing now, thanks! Compiled OK with: [csamuel@tango hwloc-0.9.1rc3r1276]$ pgcc -V pgcc 8.0-6 64-bit target on x86-64 Linux -tp gh-64 Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved. Copyright 2000-2009, STMicroelectronics, Inc

Re: [hwloc-devel] Pgcc issues fixed?

2009-11-03 Thread Chris Samuel
- "Jeff Squyres" wrote: > Try this tarball: > > http://www.open-mpi.org/~jsquyres/unofficial/hwloc-0.9.1rc3r1276.tar.bz2 Grabbing now, thanks! Sorry for not seeing the email yesterday, it was a public holiday here yesterday (Melbourne Cup Day, yes we have a public holiday for a horse race

Re: [hwloc-devel] Pgcc issues fixed?

2009-11-03 Thread Chris Samuel
- "Jeff Squyres (jsquyres)" wrote: > Pgcc issues fixed? Sorry folks, have not yet got the SVN checkout to configure yet due to it requiring newer tools than I have and am buried trying to get board reports out at present. Hopefully will have some time tomorrow 2-3pm my time. If it's any h

Re: [hwloc-devel] hwloc-0.9.1rc3 fails with pgcc

2009-10-30 Thread Chris Samuel
- "Pavan Balaji" wrote: > Log files attached. Hmm, it compiled for me with pgcc! [csamuel@tango hwloc-0.9.1rc3]$ pgcc -V pgcc 9.0-4 64-bit target on x86-64 Linux -tp shanghai-64 Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved. Copyright 2000-2009, STMicroelectronics, In

Re: [hwloc-devel] 0.9.1rc3 has been released

2009-10-30 Thread Chris Samuel
- "Jeff Squyres" wrote: > I tweaked this a bit -- how's this: Looks good to me! -- Christopher Samuel - (03) 9925 4751 - Systems Manager The Victorian Partnership for Advanced Computing P.O. Box 201, Carlton South, VIC 3053, Australia VPAC is a not-for-profit Registered Research Agency

Re: [hwloc-devel] [OMPI devel] 0.9.1rc2 is available

2009-10-22 Thread Chris Samuel
- "Tony Breeds" wrote: > Powerpc kernels that old do not have the topology information needed > (in /sys or /proc/cpuinfo) So for the short term that's be best we > can do. That's fine, I quite understand. I'm trying to get that cluster replaced anyway.. ;-) > FWIW I'm looking at how we