Hi,
I've tried the port on by macbook which has a intel core 2 duo chip and my imac
which has an intel core duo nad I get the same error.
I have yet to talk to the developers
Glenn
CC:
macports-users@lists.macosforge.org From: [EMAIL PROTECTED]
Jason,
I reckon that your problems will be solved by fixing the last export
PATH. Unless it's a typo in your email, it appears that you forgot
the :$PATH at the end of your last export PATH.
There's a priority in the ordering that's normally not super-critical.
In your case, if you want
Ok, I reverted to the original Apple sed. That helped, but the
install failed again. Here are the last few lines of the log:
...
/usr/bin/ld: multiple definitions of symbol _g_malloc0
/opt/local/lib/libglib-2.0.dylib(gmem.o) definition of _g_malloc0
I have setup dozens of Linux and FreeBSD machines with gpg-agent. But,
doing it on a Mac seems to be voodoo at best. I think that every howto and
thread that Google turns up is missing some extremely important
prerequisites. Quite honestly, I feel like I am trashing my system with all
the
I'm trying to get Python 2.5 installed but get this error in return.
I'm running:
Macports Version: 1.520
Mac OS X (PPC) 10.4.10
Xcode Version: 2.4.1
root# port install python25
--- Fetching python25
--- Verifying checksum(s) for python25
--- Extracting python25
--- Applying patches to
PortAuthority 2.4, my GUI for MacPorts, is now available. This version
includes several bug fixes and new features to improve the user
experience when first trying the application, and also fixes some minor
UI bugs. For more information and to download, see
How does one go about installing php_dabse for the php5 package? And
for that matter, how does one go about installing any of the other php
extensions that are commented out in the php.ini file?
Thanks for the help!
-Abe
___
macports-users mailing list
If I try to install anything using interactive mode (e.g. first doing a
sudo port -v -d and then once I'm at the console, typing install
curl), I get the following error. However, if I do it all from the
command line (e.g. sudo port -d -v install curl) it works fine...
alloc: invalid block:
