On Thu, 2009-08-27 at 23:46 -0400, Greg Watson wrote:
> I didn't realize it would be such a problem. Unfortunately there is
> simply no way to reliably parse this kind of output, because it is
> impossible to know what the error messages are going to be, and
> presumably they could include XML-like
On Aug 27, 2009, at 9:45 PM, Eugene Loh wrote:
Good point. I'm a dummy about these things. Assuming I know how to
fix
what you're saying, I inserted a "rehash" in my script after "make
install", but still got the same problem. That is, the relevent
part of
the script now says:
foreach P
Ralph,
Would this be doable? If we could guarantee that the only output that
went to the file was XML then that would solve the problem.
Greg
On Aug 28, 2009, at 5:39 AM, Ashley Pittman wrote:
On Thu, 2009-08-27 at 23:46 -0400, Greg Watson wrote:
I didn't realize it would be such a proble
Hi Tim, Eugene,
Actually, the part about not needing to run autogen.sh; if running
via a nightly/release tarball is not entirely accurate. The tarballs
are configured to allow parallel builds (e.g., "gmake -j6 ..."); however,
when you run autogen.sh when building in an older Lustre filesystem,
The easiest way to do this is to install all the Autotools (Autoconf,
Automake, Libtool, m4) into a single $prefix. That way, you don't
have to copy *.m4 files around (I don't know what distros do by
default -- I typically install my own/very recent Auto tools under
$HOME/new-gnu or somesu
