1. On an admittedly pre-production Cisco sandy bridge server, I ran "lstopo
foo.xml", which ended up putting a ctrl-A in the value of the following line:
<info name="DMIProductVersion" value=""/>
I.e., the value was quote ^A quote. This caused barfage when trying to use
that xml file as input to lstopo (it called it an illegal character).
Should we filter characters that we know the input parser won't accept?
2. Somehow, when I configure and build the hwloc trunk on my mac, it won't
provide any graphical output formats. But when I configure and build the hwloc
1.4 branch on my mac, all the graphical output formats are supported. This is
at the HEAD of both:
-----
[10:50] jsquyres-mac:~/svn/hwloc % ./utils/lstopo --help | grep Supported
Supported output file formats: console, txt, fig, xml, synthetic
[10:50] jsquyres-mac:~/svn/hwloc % cd ../hwloc-1.4/
[10:50] jsquyres-mac:~/svn/hwloc-1.4 % ./utils/lstopo --help | grep Supported
Supported output file formats: console, txt, fig, pdf, ps, png, svg, xml,
synthetic
[10:50] jsquyres-mac:~/svn/hwloc-1.4 %
-----
What changed? The stdout from configure doesn't show any major differences;
Cairo is found on both (and they're both obviously using the same Cairo).
I'm pretty sure I've used the trunk hwloc to output a PDF on my mac within the
last 2-3 weeks.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
