Installing python25 on OS X 10.3 failed
Hi, I was trying to install python25 but I've got errors below ranlib libpython2.5.a 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 -L/opt/local/lib ld: for architecture ppc ld: warning prebinding disabled because of undefined symbols ld: Undefined symbols: restFP saveFP libtool: internal link edit command failed make: *** [libpython2.5.dylib] Error 1 Error: Status 1 encountered during processing. When I fetch python && configure && make myself, that works without any problem. Any Idea?
Created trac ticket for this. http://trac.macports.org/projects/macports/ticket/13322#comment:2 Nox, Changeset 29606 seems to have something to do with this problem. http://trac.macports.org/projects/macports/changeset/29606 But I'm not sure why above changes make python build fails. Could you give me a hand to solve this, please?
Hi ebgssth@gmail.com, 10.3 is not officially supported anymore*) and I do not even have access to a 10.3 box. I'll happily add any patch for 10.3 that does not conflict with 10.4 or 10.5 but I don't have a way of testing it. -Markus *) which doesn't mean anyone will break stuff on purpose On 17.11.2007, at 11:58, js wrote:
Created trac ticket for this. http://trac.macports.org/projects/macports/ticket/13322#comment:2
Nox, Changeset 29606 seems to have something to do with this problem. http://trac.macports.org/projects/macports/changeset/29606
But I'm not sure why above changes make python build fails. Could you give me a hand to solve this, please?
--- Markus W. Weissmann http://www.mweissmann.de/
I have X11, XCode tools (from the Leopard disc) and MacPorts 1.5.0-10.5 installed but when I run the command: Sudo port -dv selfupdate I get this output: DEBUG: Rebuilding the MacPorts base system if needed. DEBUG: Synchronizing ports tree(s) Synchronizing from rsync://rsync.macports.org/release/ports/ DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/ports/ /opt/local/var/macports/sources/rsync.macports.org/release/ports rsync: failed to connect to rsync.macports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-30/rsync/clientserver.c(94) DEBUG: Couldn't sync the ports tree: sync failed doing rsync while executing "macports::selfupdate [array get global_options]" Error: /opt/local/bin/port: selfupdate failed: Couldn't sync the ports tree: sync failed doing rsync I made sure that this machine has unrestricted access to the 'net through the firewall. Does anyone know why this isn't updating? Thanks for the help! Chad
On Nov 19, 2007 8:47 PM, Boyd, Chad <CBoyd@madden.com> wrote:
I have X11, XCode tools (from the Leopard disc) and MacPorts 1.5.0-10.5installed but when I run the command:
Sudo port -dv selfupdate
I get this output:
DEBUG: Rebuilding the MacPorts base system if needed. DEBUG: Synchronizing ports tree(s) Synchronizing from rsync://rsync.macports.org/release/ports/ DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/ports/ /opt/local/var/macports/sources/rsync.macports.org/release/ports rsync: failed to connect to rsync.macports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-30/rsync/clientserver.c(94) DEBUG: Couldn't sync the ports tree: sync failed doing rsync while executing "macports::selfupdate [array get global_options]" Error: /opt/local/bin/port: selfupdate failed: Couldn't sync the ports tree: sync failed doing rsync
are you running PeerGuardian? try disabling it and see if it works...
This appears to have been a firewall issue. My updates to my ACL's weren't taking. I fixed that and am now able to download the updates. ________________________________ From: immram [mailto:immram@gmail.com] Sent: Monday, November 19, 2007 2:53 PM To: Boyd, Chad Cc: macports-users@lists.macosforge.org Subject: Re: MacPorts not updating on Leopard On Nov 19, 2007 8:47 PM, Boyd, Chad <CBoyd@madden.com<mailto:CBoyd@madden.com>> wrote: I have X11, XCode tools (from the Leopard disc) and MacPorts 1.5.0-10.5 installed but when I run the command: Sudo port -dv selfupdate I get this output: DEBUG: Rebuilding the MacPorts base system if needed. DEBUG: Synchronizing ports tree(s) Synchronizing from rsync://rsync.macports.org/release/ports/ DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/ports/ /opt/local/var/macports/sources/rsync.macports.org/release/ports rsync: failed to connect to rsync.macports.org<http://rsync.macports.org>: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-30/rsync/clientserver.c(94) DEBUG: Couldn't sync the ports tree: sync failed doing rsync while executing "macports::selfupdate [array get global_options]" Error: /opt/local/bin/port: selfupdate failed: Couldn't sync the ports tree: sync failed doing rsync are you running PeerGuardian? try disabling it and see if it works...
On Nov 19, 2007, at 14:02, Weissmann Markus wrote:
10.3 is not officially supported anymore*) and I do not even have access to a 10.3 box. I'll happily add any patch for 10.3 that does not conflict with 10.4 or 10.5 but I don't have a way of testing it.
-Markus
*) which doesn't mean anyone will break stuff on purpose
This is the first I've heard of 10.3 not being supported anymore. Historically MacPorts has supported the current Mac OS X release and the previous one, and granted, 10.5 was just released. But a lot of ports aren't working so great on Leopard right now [1]. If a decision is made to drop 10.3 support, I would hope that we would wait until the 10.5 bug reports stop bucketing in and we can honestly say that the MacPorts experience on 10.5 is at least as good as it was on 10.4. And we are currently far from that. Note that the new guide [2] does not seem to indicate what versions of Mac OS X are supported. It should so indicate, fairly near the top. [1] http://trac.macports.org/projects/macports/query? status=new&status=assigned&status=reopened&summary=% 7Eleopard&order=priority [2] http://geeklair.net/new_macports_guide/
Ryan Schmidt wrote:
On Nov 19, 2007, at 14:02, Weissmann Markus wrote:
10.3 is not officially supported anymore*) and I do not even have access to a 10.3 box.
This is the first I've heard of 10.3 not being supported anymore.
Historically MacPorts has supported the current Mac OS X release and the previous one, and granted, 10.5 was just released. But a lot of ports aren't working so great on Leopard right now [1]. If a decision is made to drop 10.3 support, I would hope that we would wait until the 10.5 bug reports stop bucketing in and we can honestly say that the MacPorts experience on 10.5 is at least as good as it was on 10.4. And we are currently far from that.
Last thing I heard was that support for *Jaguar* and OpenDarwin was to be dropped (a lot of ports still have "darwin 6" and "puredarwin" blocks), but that Panther would continue to be supported - even if Apple doesn't really issue updates for it anymore. At least historically, kitty-2 dies* when the new one is born. Outside of MacPorts, I'm still supporting Mac OS X 10.3 "while stock lasts" but that is mostly because the SDKs and Rosetta make it possible to build and test somewhat on Leopard even... (and partly because I think Panther has probably been the best Mac OS X release so far for me, out of the five - as I'm still using it) --anders PS. Just noticed that they pulled the link to Mac OS X 10.4 too, http://www.apple.com/macosx/tiger/ ...
Apple is still supporting 10.3 updates to itunes, quicktime and security are regular. I hope it will still be supported by macports as well. Marco On Nov 20, 2007, at 2:40 AM, Anders F Björklund wrote:
Ryan Schmidt wrote:
On Nov 19, 2007, at 14:02, Weissmann Markus wrote:
10.3 is not officially supported anymore*) and I do not even have access to a 10.3 box.
This is the first I've heard of 10.3 not being supported anymore.
Historically MacPorts has supported the current Mac OS X release and the previous one, and granted, 10.5 was just released. But a lot of ports aren't working so great on Leopard right now [1]. If a decision is made to drop 10.3 support, I would hope that we would wait until the 10.5 bug reports stop bucketing in and we can honestly say that the MacPorts experience on 10.5 is at least as good as it was on 10.4. And we are currently far from that.
Last thing I heard was that support for *Jaguar* and OpenDarwin was to be dropped (a lot of ports still have "darwin 6" and "puredarwin" blocks), but that Panther would continue to be supported - even if Apple doesn't really issue updates for it anymore. At least historically, kitty-2 dies* when the new one is born.
Outside of MacPorts, I'm still supporting Mac OS X 10.3 "while stock lasts" but that is mostly because the SDKs and Rosetta make it possible to build and test somewhat on Leopard even... (and partly because I think Panther has probably been the best Mac OS X release so far for me, out of the five - as I'm still using it)
--anders
PS. Just noticed that they pulled the link to Mac OS X 10.4 too, http://www.apple.com/macosx/tiger/ ...
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Sadly, there's no way to figure out how many OS X 10.3 users exist. This number is probably the most important one to take into account deciding whether MacPorts should support OS X 10.3 or not. Assuming Apple supports OSs as long as there're fair amount of users, this might be a good idea to support MacPorts on OSs Apple officially supports. (10.3 - 10.5?) Letting Apple decidess it might be a better On Nov 20, 2007 7:30 AM, Ryan Schmidt <ryandesign@macports.org> wrote:
On Nov 19, 2007, at 14:02, Weissmann Markus wrote:
10.3 is not officially supported anymore*) and I do not even have access to a 10.3 box. I'll happily add any patch for 10.3 that does not conflict with 10.4 or 10.5 but I don't have a way of testing it.
-Markus
*) which doesn't mean anyone will break stuff on purpose
This is the first I've heard of 10.3 not being supported anymore.
Historically MacPorts has supported the current Mac OS X release and the previous one, and granted, 10.5 was just released. But a lot of ports aren't working so great on Leopard right now [1]. If a decision is made to drop 10.3 support, I would hope that we would wait until the 10.5 bug reports stop bucketing in and we can honestly say that the MacPorts experience on 10.5 is at least as good as it was on 10.4. And we are currently far from that.
Note that the new guide [2] does not seem to indicate what versions of Mac OS X are supported. It should so indicate, fairly near the top.
[1] http://trac.macports.org/projects/macports/query? status=new&status=assigned&status=reopened&summary=% 7Eleopard&order=priority
"Official" MacPorts policy has been that we support the two most recent versions of Mac OS. Which at the present means Tiger and Leopard. That doesn't mean that we'll go out of our way to break older versions, but that we don't promise we won't. A particularly good example of why this is probably a good idea is the current situation where we'd like to add additional support for launchd and startupitems. Launchd wasn't available on Panther, and to add new support for launchd startupitems will likely mean that ports relying on the feature will gradually become inoperable on Panther, where it will be too hard to maintain compatibility using SystemStarter features. To continue supporting a the 3-year-old Panther OS would mean restricting support for the newer versions, or creating an overly-complicated implementation. James On Nov 22, 2007, at 6:16 AM, js wrote:
Sadly, there's no way to figure out how many OS X 10.3 users exist. This number is probably the most important one to take into account deciding whether MacPorts should support OS X 10.3 or not. Assuming Apple supports OSs as long as there're fair amount of users, this might be a good idea to support MacPorts on OSs Apple officially supports. (10.3 - 10.5?)
Letting Apple decidess it might be a better
On Nov 20, 2007 7:30 AM, Ryan Schmidt <ryandesign@macports.org> wrote:
On Nov 19, 2007, at 14:02, Weissmann Markus wrote:
10.3 is not officially supported anymore*) and I do not even have access to a 10.3 box. I'll happily add any patch for 10.3 that does not conflict with 10.4 or 10.5 but I don't have a way of testing it.
-Markus
*) which doesn't mean anyone will break stuff on purpose
This is the first I've heard of 10.3 not being supported anymore.
Historically MacPorts has supported the current Mac OS X release and the previous one, and granted, 10.5 was just released. But a lot of ports aren't working so great on Leopard right now [1]. If a decision is made to drop 10.3 support, I would hope that we would wait until the 10.5 bug reports stop bucketing in and we can honestly say that the MacPorts experience on 10.5 is at least as good as it was on 10.4. And we are currently far from that.
Note that the new guide [2] does not seem to indicate what versions of Mac OS X are supported. It should so indicate, fairly near the top.
[1] http://trac.macports.org/projects/macports/query? status=new&status=assigned&status=reopened&summary=% 7Eleopard&order=priority
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
BTW, Does "Official support" mean anything? Just another name of priority? On Nov 22, 2007 11:48 PM, James Berry <jberry@macports.org> wrote:
"Official" MacPorts policy has been that we support the two most recent versions of Mac OS. Which at the present means Tiger and Leopard. That doesn't mean that we'll go out of our way to break older versions, but that we don't promise we won't.
A particularly good example of why this is probably a good idea is the current situation where we'd like to add additional support for launchd and startupitems. Launchd wasn't available on Panther, and to add new support for launchd startupitems will likely mean that ports relying on the feature will gradually become inoperable on Panther, where it will be too hard to maintain compatibility using SystemStarter features. To continue supporting a the 3-year-old Panther OS would mean restricting support for the newer versions, or creating an overly-complicated implementation.
James
On Nov 22, 2007, at 6:16 AM, js wrote:
Sadly, there's no way to figure out how many OS X 10.3 users exist. This number is probably the most important one to take into account deciding whether MacPorts should support OS X 10.3 or not. Assuming Apple supports OSs as long as there're fair amount of users, this might be a good idea to support MacPorts on OSs Apple officially supports. (10.3 - 10.5?)
Letting Apple decidess it might be a better
On Nov 20, 2007 7:30 AM, Ryan Schmidt <ryandesign@macports.org> wrote:
On Nov 19, 2007, at 14:02, Weissmann Markus wrote:
10.3 is not officially supported anymore*) and I do not even have access to a 10.3 box. I'll happily add any patch for 10.3 that does not conflict with 10.4 or 10.5 but I don't have a way of testing it.
-Markus
*) which doesn't mean anyone will break stuff on purpose
This is the first I've heard of 10.3 not being supported anymore.
Historically MacPorts has supported the current Mac OS X release and the previous one, and granted, 10.5 was just released. But a lot of ports aren't working so great on Leopard right now [1]. If a decision is made to drop 10.3 support, I would hope that we would wait until the 10.5 bug reports stop bucketing in and we can honestly say that the MacPorts experience on 10.5 is at least as good as it was on 10.4. And we are currently far from that.
Note that the new guide [2] does not seem to indicate what versions of Mac OS X are supported. It should so indicate, fairly near the top.
[1] http://trac.macports.org/projects/macports/query? status=new&status=assigned&status=reopened&summary=% 7Eleopard&order=priority
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
On Nov 22, 2007, at 7:26 AM, js wrote:
BTW, Does "Official support" mean anything? Just another name of priority?
I said "official" policy, not official support. MacPorts provides no official support for anything, though unofficial and informal support is available through this email list and the irc channel. ;) The use of the work "support" in my mail below can all be considered to mean "is able to work with", rather than "technical support." James
On Nov 22, 2007 11:48 PM, James Berry <jberry@macports.org> wrote:
"Official" MacPorts policy has been that we support the two most recent versions of Mac OS. Which at the present means Tiger and Leopard. That doesn't mean that we'll go out of our way to break older versions, but that we don't promise we won't.
A particularly good example of why this is probably a good idea is the current situation where we'd like to add additional support for launchd and startupitems. Launchd wasn't available on Panther, and to add new support for launchd startupitems will likely mean that ports relying on the feature will gradually become inoperable on Panther, where it will be too hard to maintain compatibility using SystemStarter features. To continue supporting a the 3-year-old Panther OS would mean restricting support for the newer versions, or creating an overly-complicated implementation.
James
On Nov 22, 2007, at 6:16 AM, js wrote:
Sadly, there's no way to figure out how many OS X 10.3 users exist. This number is probably the most important one to take into account deciding whether MacPorts should support OS X 10.3 or not. Assuming Apple supports OSs as long as there're fair amount of users, this might be a good idea to support MacPorts on OSs Apple officially supports. (10.3 - 10.5?)
Letting Apple decidess it might be a better
On Nov 20, 2007 7:30 AM, Ryan Schmidt <ryandesign@macports.org> wrote:
On Nov 19, 2007, at 14:02, Weissmann Markus wrote:
10.3 is not officially supported anymore*) and I do not even have access to a 10.3 box. I'll happily add any patch for 10.3 that does not conflict with 10.4 or 10.5 but I don't have a way of testing it.
-Markus
*) which doesn't mean anyone will break stuff on purpose
This is the first I've heard of 10.3 not being supported anymore.
Historically MacPorts has supported the current Mac OS X release and the previous one, and granted, 10.5 was just released. But a lot of ports aren't working so great on Leopard right now [1]. If a decision is made to drop 10.3 support, I would hope that we would wait until the 10.5 bug reports stop bucketing in and we can honestly say that the MacPorts experience on 10.5 is at least as good as it was on 10.4. And we are currently far from that.
Note that the new guide [2] does not seem to indicate what versions of Mac OS X are supported. It should so indicate, fairly near the top.
[1] http://trac.macports.org/projects/macports/query? status=new&status=assigned&status=reopened&summary=% 7Eleopard&order=priority
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
participants (8)
-
Anders F Björklund
-
Boyd, Chad
-
immram
-
James Berry
-
js
-
Marco Battistella
-
Ryan Schmidt
-
Weissmann Markus