Changes between Initial Version and Version 2 of Ticket #49168
- Timestamp:
- Oct 8, 2015, 2:47:38 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #49168
-
Property
Status
changed from
new
toclosed
- Property Keywords selfupdate removed
-
Property
Resolution
changed from
to
duplicate
-
Property
Status
changed from
-
Ticket #49168 – Description
initial v2 1 1 I am getting an error when running port selfupdate and this machine's self update was reliable from this network in the past. Please note that my rsync appeared to work, hence it is likely different than Ticket #49140, which has a similar complaint but probably a different cause. Here I try it twice (note the user name is sanitized), the second time with the -v flag. Interestingly I the error appears to complain about the C compiler unable to create executables, but port installed shows "gcc49 @4.9.3_0 (active)", I've appended the full list to the end of this description. The file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base/config.log is attached. 2 2 3 {{{ 3 4 My-MacBook-Pro-2:tmp FoolishEwe$ sudo port selfupdate 4 5 ---> Updating MacPorts base sources using rsync … … 65 66 http://guide.macports.org/#project.tickets 66 67 Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed 68 }}} 67 69 68 70 Here is the output of port install 71 {{{ 69 72 port installed 70 73 The following ports are currently installed: … … 814 817 yasm @1.3.0_0 (active) 815 818 zlib @1.2.8_0 (active) 819 }}}