The only +universal I used was on python25 itself after the GIMP
install first started giving me that error, and I think it resulted
in the same error again. That's when I gave the "maybe it checks for
dependencies independently of installing them" chance a try with
the .mpkg, and as you said, that was futile.
On 25-Oct-07, at 3:25 PM, Ryan Schmidt wrote:
On Oct 25, 2007, at 14:24, Fred Brown Althot wrote:
On 25-Oct-07, at 2:41 PM, Ryan Schmidt wrote:
On Oct 25, 2007, at 12:57, Fred Brown Althot wrote:
When trying to install the GIMP, I get this little nasty:
freds-computer:~ fred$ sudo port install -f gimp-app
Password:
---> Building python25 with target all
Error: Target org.macports.build returned: shell command " cd "/
opt/local/var/macports/build/
_opt_local_var_macports_sources_rsync.macports.org_release_ports_l
ang_python25/work/Python-2.5.1" && make all " returned error 2
Command output: libtool -o libpython2.5.dylib -dynamic \
-all_load libpython2.5.a -single_module \
-install_name /opt/local/lib/libpython2.5.dylib \
-compatibility_version 2.5 \
-current_version 2.5 -lSystem -lSystemStubs -L/opt/
local/lib
ld64 failed: in libpython2.5.a(__.SYMDEF), not a valid ppc64
mach-o file
libtool: internal link edit command failed
make: *** [libpython2.5.dylib] Error 1
Error: The following dependencies failed to build: gimp2 py25-
gtk py25-cairo py25-numeric python25 py25-gobject
Error: Status 1 encountered during processing.
Now, I tried installing python 2.5 independently with a package,
that seemed to work fine, but I still get the same error (I was
hoping it would detect the installed dependency and move on, but
alas, it does not).
Any help overcoming this setback would be greatly appreciated,
because I'm running out of ideas right now.
You are presumably on a 64-bit PowerPC machine, as in a G5? What
version of Mac OS X, Xcode and MacPorts are you using?
Actually, I'm on an Intel mac.
Sorry, should have mentioned that from the start.
Intel Mac, OS X 10.4
Using the latest version of macports.
After running into this problem, I tried installing the universal
macpython 2.5.1 with the .mpkg, ran port install again, same problem.
MacPorts is designed to use its own software only, not any software
you've installed manually outside of MacPorts. There are some
carefully-chosed exceptions, but I don't think python is one of them.
So if you're not on a 64-bit PowerPC machine, I wonder why it's
complaining that something is not a valid ppc64 mach-o file. Are
any of your ports compiled universally? (Did you say "sudo port
install foo +universal" for any foo?)
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
