Re: problem with multiple macports installations
Hi Dan, The macoprt.conf files in /opt/local and and /opt/local64 only reference /opt/local and /opt/local64 respectively, so this seems correct. 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? Daniel Am 18.12.2007 um 19:51 schrieb Daniel J. Luke:
Did you check your ${prefix}/etc/macports/macports.conf file? the prefix and/or portdbpath may have gotten munged.
-- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
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. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
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 +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On 2007-December-18 , at 20:15 , Daniel J. Luke wrote:
On Dec 18, 2007, at 2:10 PM, Daniel J. Luke wrote:
On Dec 18, 2007, at 2:06 PM, Daniel Oberhoff wrote:
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.
Hi, could you elaborate a bit on that. I have the exact same problem with: - two macport trees: /opt/local/ installed as a regular install and / opt/local-exp installed from source with --prefix=/opt/local-exp/ - no ~/.macports - the sources in both ${prefix}/etc/macports.conf are pointing to the correct location and still the port command in /opt/local/bin/port lists the content of /opt/local-exp/ Thanks in advance. JiHO --- http://jo.irisson.free.fr/
On Dec 18, 2007, at 3:55 PM, jiho wrote:
if you didn't build with --with-tclpackage set so that your two installs have separate package directories, that could be causing your problem.
Hi, could you elaborate a bit on that. I have the exact same problem with: - two macport trees: /opt/local/ installed as a regular install and / opt/local-exp installed from source with --prefix=/opt/local-exp/ - no ~/.macports - the sources in both ${prefix}/etc/macports.conf are pointing to the correct location and still the port command in /opt/local/bin/port lists the content of /opt/local-exp/
You need to rebuild port (ideally twice). Soemthing like: ./configure --prefix=/opt/local --with-tclpackage=/opt/local/share/tcl and ./configure --prefix=/opt/local-exp --with-tclpackage=/opt/local-exp/ share/tcl should work -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On 2007-December-18 , at 21:58 , Daniel J. Luke wrote:
On Dec 18, 2007, at 3:55 PM, jiho wrote:
if you didn't build with --with-tclpackage set so that your two installs have separate package directories, that could be causing your problem.
Hi, could you elaborate a bit on that. I have the exact same problem with: - two macport trees: /opt/local/ installed as a regular install and /opt/local-exp installed from source with --prefix=/opt/local- exp/ - no ~/.macports - the sources in both ${prefix}/etc/macports.conf are pointing to the correct location and still the port command in /opt/local/bin/port lists the content of /opt/local-exp/
You need to rebuild port (ideally twice).
Soemthing like:
./configure --prefix=/opt/local --with-tclpackage=/opt/local/share/tcl and ./configure --prefix=/opt/local-exp --with-tclpackage=/opt/local-exp/ share/tcl
should work
Thanks it works indeed. I've only done the first one and everything seems to be working correctly. I'll do the second install too anyway, just to be sure and because I need to upgrade it to 1.6 no matter what. Thanks again (IMHO, this deserves a FAQ somewhere) JiHO --- http://jo.irisson.free.fr/
I also got it done that way now. Just had to take care to save my original installations (i.e. move them out of the way and later move them back). Otherwise the installation starts to do a lot of linking...whatever. Seems to work :). So now I have one 32 bit tree and one 64bit. So far ok. Just annoying since I have to specify the right flags at the command line everytime (defaults in macport.tcl seem to be ignored) and some packages don't use configure but patched makefiles which requires some handwork. General suggestion: it would be nice if there would be a 64bit variant, and the possibility to stack variants (i.e. something like +ppc +64). Just my 2 cents. Best Daniel Am 18.12.2007 um 22:30 schrieb jiho:
On 2007-December-18 , at 21:58 , Daniel J. Luke wrote:
On Dec 18, 2007, at 3:55 PM, jiho wrote:
if you didn't build with --with-tclpackage set so that your two installs have separate package directories, that could be causing your problem.
Hi, could you elaborate a bit on that. I have the exact same problem with: - two macport trees: /opt/local/ installed as a regular install and /opt/local-exp installed from source with --prefix=/opt/local- exp/ - no ~/.macports - the sources in both ${prefix}/etc/macports.conf are pointing to the correct location and still the port command in /opt/local/bin/port lists the content of /opt/local-exp/
You need to rebuild port (ideally twice).
Soemthing like:
./configure --prefix=/opt/local --with-tclpackage=/opt/local/share/ tcl and ./configure --prefix=/opt/local-exp --with-tclpackage=/opt/local- exp/share/tcl
should work
Thanks it works indeed. I've only done the first one and everything seems to be working correctly. I'll do the second install too anyway, just to be sure and because I need to upgrade it to 1.6 no matter what. Thanks again (IMHO, this deserves a FAQ somewhere)
JiHO --- http://jo.irisson.free.fr/
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
participants (3)
-
Daniel J. Luke
-
Daniel Oberhoff
-
jiho