Re: [PerfSuite-users] Problem with psconfig, workaround for building a config file?

[Rick K. <rk...@nc...>]

Tyler - hopefully it is simple to get you past this hurdle, although
as you point out, documentation for psconfig is lacking (sorry).

In general, psconfig isn't really necessary to do performance measurement
with psrun or the API, whether you have PAPI or not.  If the installation
completes successfully, "psrun <somecommand>" should run without errors,
and you should be able to use psprocess on the resulting XML document
to view the data.  If the XML doc contains profiling data, you'll
also have to supply the name of the executable to psprocess, with the
option -e.

Alternate XML config files, including samples without PAPI, should
be installed in the directory PREFIX/share/perfsuite/xml/pshwpc,
and there is a sample config file called "profil.xml" that might
help out here.  You might try:

  psrun -c profil.xml a.out
  psprocess -e a.out yourxmlfile.xml

You might need to supply the full path to profil.xml for things to
work properly with your install.

Again, use of psconfig is completely optional and not necessary.
However, there isn't enough info here to see if in fact your tDOM
install isn't correct.  If it isn't, then psprocess will have problems
(probably will not be able to find/load tDOM).  psrun doesn't use
tDOM, so the use of an alternate XML config is independent of tDOM.

The INSTALL file has some information about install/build of tDOM and
use of "configure" that might help see what might be the problem as
well.  If still stuck, then some sample error output might help and
also the exact configure line you used (it should be stored in 
config.log).

Hope this helps track things down,

Rick

On Thu, 7 Apr 2005 ol...@ec... wrote:

> I'm trying to do some performance analysis on a quad-processor Intel Xeon
> 1.80Ghz machine. I've spent nearly the last two weeks trying to build a
> configuration input file for perfsuite for this machine and psconfig refuses to
> run because it detects a problem with the tDOM installation. I've done
> absolutely everything I can to try and install tDOM properly, but it just will
> not work correctly and the documentation for that software package is absolutely
> horrible, so I have no idea how to fix it.
> 
> 
> What I would like to know is, is there an easy way to build a configuration file
> *without* using psconfig? If not, is there some documentation about how the
> configuration files are structured, because at this point it would be much
> easier/faster to just write the XML file myself by hand. (An example
> configuration file *without* PAPI would be wonderful to look at). Thank you for
> any help you can provide.
> 
> 
> - Tyler Olsen