#39752: tcl @8.6.0's tclConfig.sh script contains MacPorts build directories ----------------------+-------------------- Reporter: egall@… | Owner: mww@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: invalid | Keywords: Port: tcl | ----------------------+-------------------- Comment (by cal@…): Replying to [comment:4 egall@…]:
I think that actually might have been what I was trying to do (I have a copy of Tcl in-tree for my fork of apple-gdb, for use with gdbtk), and I think that I must have just forgot to tell it to use the in-tree one instead of the MacPorts one... although then again, if this is from 8 months ago, I do not think that I had actually started work on that by that point, so maybe it was for something different, I forget...
Make sure that right next to the tclConfig.sh file picked up by your configure script there also is a Makefile. That's the test tcl.m4 uses to determine whether to use the build variables.
The macros in the standard `tcl.m4` are also pretty out-of-date, so I usually modify the copy I use to bring it more up-to-date, and it is possible that one of these modifications might have accidentally messed up the variables that it chose... anyway, either way it was probably a user error on my part, so I am okay with the closing of this.
In what way are the macros in tcl.m4 out of date? -- Ticket URL: <https://trac.macports.org/ticket/39752#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X