Re: building snapshot on hp-ux with hp tools

[mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)]

> Historically expect and dejagnu have been bundled in with GDB to ensure 
> that all parties are using a consistent test framework.  It might be 
> time to cut our losses?

Gcc has an "unbundled" strategy, so every gcc tester has to install
tcl+expect+dejagnu outside of gcc.  It works for them; they have a lot
of testing activity.  Look at http://gcc.gnu.org/ml/gcc-testresults .
I wish that gdb-testers looked like that.

> Does a more up-to-date expect build?

Errr, no.  expect 5.39 does not build on hppa2.0w-hp-hpux11.11 with
the hp ansi c compiler.  Configure craps out with:

  checking whether the compiler (gcc -pipe) actually works... configure:
  error: the native compiler is broken and won't compile.

I don't know what the gcc-testresults@ people are doing to work
around that.  Perhaps they always use gcc to build tcl+expect+dejagnu.

If we unbundle tcl+expect+dejagnu, then we can separate those problems
out.  As it is, I can't tell people to try gdb snapshots on hp-ux
(see pr gdb/1458, I can't reply to it with "try a snapshot").

The advantage of bundling is that, in principle, we can make things
easier for people, if add value to our bundled versions.  The
disadvantage of bundling is that we're not spending the effort to add
value so that the "+dejagnu" part of "gdb+dejagnu" just stops it from
building on some systems.

I'm favor of separating gdb from dejagnu.  Have a separate
"tcl+expect+dejagnu" tarball if you want, but no "gdb+dejagnu".

Michael C