Norman,
> Have you at some point run autoconf in the top-level directory?
Not knowingly.
> That dummy prefix _shouldn't_ be propagated to subdirectories, and
> appears not to be (in my tree), but I wouldn't like to claim that it
> _cannot_ be. Are you saying that the unsubstituted prefix has made
> its way into the tclsys ./configure file (I'm not sure what directory
> you're in in your message)?
Yes. I first encountered it during a "make world" when itreached
tclsys/tclx.
> in cunning, which that script is not currently short of. If you've
> found a way of breaking this, however, I can harden the script
> appropriately -- no problem.
Not knowingly. I just went through the normal procedures, but these
weren't enough for tclsys at first. I had built tclsys recenty since
the bulk of Peter's changes, but then GAIA build failed. Somewhere in
this mess the prefix got lost.
> I've modified configure.ac so that the generated ./configure traps
> the case where the prefix has not been substituted (someone has run
> autoconf outside of ./bootstrap), and indicates what to do; and I've
> improved the explanation in ./bootstrap.
Thank you kind sir. The "indicates what to do" is especially welcome.
Malcolm
|