On May 8, 2008, at 9:43 PM, Shreevatsa R wrote:
The site doesn't seem to be working, so reporting a bug here:
Parts of the web site may be down or weird for a few days as William
continues to stabilize the system following the recent site upgrades.
Hopefully we'll soon be back to normal.
Shreevatsa R wrote:
The site doesn't seem to be working, so reporting a bug here:
The guide says that to install two different MacPorts copies, one must
use --with-tclpackage. But try this:
./configure --prefix=PREFIX1 --with-tclpackage=TCLPREFIX1 make
make install
./configure make make
On May 8, 2008, at 10:13 PM, Shreevatsa R wrote:
The site doesn't seem to be working, so reporting a bug here:
The guide says that to install two different MacPorts copies, one must
use --with-tclpackage. But try this:
./configure --prefix=PREFIX1 --with-tclpackage=TCLPREFIX1 make
make
Blair Zajac wrote:
I don't think we can just move the site-packages, can we? There are .so's in
there.
No, especially not because they are recorded in file_map.db to be
installed at the old location. If you just move them, they are not known
to MacPorts at all.
It would be possible to do
Anders F Björklund wrote:
Rainer Müller:
So if someone knows how to link against a framework in a custom
path, please advice.
See the -F flag. You'd still need the standard Current symlink
operational, though.
-F is documented to set the include path (like -I):
Add the framework
Rainer Müller wrote:
See the -F flag. You'd still need the standard Current symlink
operational, though.
-F is documented to set the include path (like -I):
Add the framework directory dir to the head of the list of
directories to be searched for header files.
If this works for headers,
-F is documented to set the include path (like -I):
Add the framework directory dir to the head of the list of
directories to be searched for header files.
If this works for headers, how is the linking done? In my test, it
still did not work (ld: framework not found Python) or was
linked
On Friday, May 09, 2008, at 03:45PM, Rainer Müller [EMAIL PROTECTED] wrote:
Anders F Björklund wrote:
gcc test.c -F/opt/local/Library/Frameworks -framework Python
Ah, my bad. I added the path to Python.framework instead of the parent.
Must have misread the documentation.
So, if there is no
