On May 1, 2012, at 11:24 AM, Brice Goglin wrote:
>> Should we filter characters that we know the input parser won't accept?
>
> Are you using libxml2 or the basic XML support ?
In both cases (input and output), libxml2. configure footer says:
(Mac -- input)
---
Le 01/05/2012 19:52, Jeff Squyres a écrit :
> 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:
>
>
>
> I.e., the value was quote ^A quote. This caused barfage when trying to use
> that
On May 1, 2012, at 11:15 AM, Brice Goglin wrote:
>> This is why I hate alternate command names. :-(
>
> lstopo-gui should do exactly what lstopo did last week. Did lstopo work
> on your mac last week?
Yes.
When I run lstopo-gui, it all works fine. I just forgot to use lstopo-gui
instead of
Le 01/05/2012 20:00, Jeff Squyres a écrit :
> On May 1, 2012, at 10:52 AM, Jeff Squyres wrote:
>
>> 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 graphi
On May 1, 2012, at 10:52 AM, Jeff Squyres wrote:
> 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 t
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:
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 ch
