what configuration files are read?

[Ryan Schmidt]

On Jan 2, 2008, at 08:16, Michael Stillwell wrote:

> On Jan 1, 2008 12:00 AM, Ryan Schmidt 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.

I agree. It's so unclear that I read the ./configure --help, couldn't  
figure it out, and went searching for Daniel's email (because I  
remembered seeing it before). But that doesn't help people who don't  
know to go looking for it.