On Dec 18, 2007, at 2:10 PM, Daniel J. Luke wrote:
On Dec 18, 2007, at 2:06 PM, Daniel Oberhoff wrote:The macoprt.conf files in /opt/local and and /opt/local64 only reference /opt/local and /opt/local64 respectively, so this seems correct.did you also check to make sure you don't have a conf file in ~/.macports that could be over-riding it?Hmm, so how does the port command actually know where it's tree lives? Is it hardcoded? Or does the installation put a tag somewhere on the system?${prefix} is set when macports is installed and it's put in that conf file.
it's also populated in the macports_autoconf.tcl file.if you didn't build with --with-tclpackage set so that your two installs have separate package directories, that could be causing your problem.
-- Daniel J. Luke +========================================================+ | *---------------- [EMAIL PROTECTED] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-users
