On Jan 1, 2008 12:00 AM, Ryan Schmidt <ryandesign@macports.org> wrote:
On Dec 31, 2007, at 06:48, Michael Stillwell wrote:
How does "port" figure out which configuration files to read? Mine is now trying to get configuration information from a non-existent file: [ ... ]
Issue #1: The reason why your two installations are conflicting with one another is that they both installed their Tcl components to / Library/Tcl/macports1.0, and the $HOME/scratch/ports instalation's / Library/Tcl/macports1.0 has overwritten the one from $HOME/Ports.
[ ... ]
You could bypass all the arguments and just do it yourself. You should reinstall both of your installations (or at least the /Ports one, since its /Library/Tcl/macports1.0 is gone), making sure that at least one, or perhaps both, of them put their Tcl directory elsewhere, for example:
PATH=/usr/bin:/usr/sbin:/bin:/sbin ./configure \ --prefix=$HOME/Ports \ --with-tclpackage=$HOME/Ports/share/macports/Tcl
Thanks; this worked perfectly. Is it possible to improve the --prefix documentation? "./configure --help" doesn't make it clear that 99% (but not 100%) of the installed files will go into the specified directory, and it's somewhat unexpected that the crucial missing directory of files is configured via --with-tclinclude. --M. -- http://beebo.org +44 78 2118 9049