Re: egcs testsuite & dejagnu : A special case?

[Jeffrey A Law <law@cygnus.com>]

  > I'm a bit lost in the parsing of that, but I think I know what you're
  > saying.  If I'm right, that eases the invocation of a compiler
  > installed in one of a variety of paths named after the version, to
  > keep track of things.  (I've been doing that for the past several
  > months, and boy is it worthwhile, and worth the extra typing, to just
  > *know* what version of what compiler I'm invoking at any one time.)
  > 
  > What I'm suggesting is a way to "elegantly" export, from the egcs
  > "system", a single command name that invokes the built command
  > instead of the installed command.
Thinking more about this, it basically means putting a large part of
dejagnu's target.exp & libgloss.exp into gcc itself.  That may not
be wise :-) :-)  But if someone wants to experiment and find a good
way to do it, it would be a big help for the developers.

  > Would this be worth trying to put into 1.1?  (Isn't the freeze date
  > for that coming up, like, this week?) 
I doubt it.  I think we've got more important issues to deal with for 1.1.

jeff