Karl Eichwalder <ke@suse.de> writes:
> "Stan Brown" <stanb@awod.com> writes:
> | I used teh --with-tcl and --with tk configure flags, so what's going on
> | here?
> The configure script wrongly thinks, tcl and tk are to be found at the
> same loaction.
Well, it doesn't exactly insist that the config files be in the same
directory. What it does do is assume that they will both be found in
the "auto_path" search path that's configured into 'tclsh'. Maybe
it'd be a better idea to look for a 'wish' and ask it its auto_path
when looking for the Tk configure info.
That's not gonna be easy, however, since 'wish' won't fire up unless it
can connect to an X display. I don't think we want to have a configure
script that fails (or delivers different results) depending on whether
you are running it inside an X session or not.
I'm also worried that we risk selecting incompatible versions of Tcl
and Tk, which would be bad news indeed. In any reasonable installation
Tcl and Tk will have similar auto_path settings; you'd have to go out
of your way during configure/build to make them different. If we don't
find the Tk configure file on the Tcl auto_path, I'd take that as a
strong sign that we've not found the Tcl that goes with Tk. (As a
person with several different Tcl/Tk versions installed on my system,
I take this concern pretty seriously...)
I'm inclined to leave the code alone and tell people with weird
Tcl/Tk layouts that they have to provide --with-tclconfig='search path'.
The code and docs do need improved to make it clear that more than one
directory can be listed in --with-tclconfig.
regards, tom lane
