Opened 9 years ago

Closed 8 years ago

#45574 closed defect (fixed)

ld64-236.3_1+llvm35.darwin_14.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified

Reported by: mehmetalierturk@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.2
Keywords: yosemite Cc:
Port: ld64

Description (last modified by ryandesign (Ryan Carsten Schmidt))

While installing gcc47, ports cannot find "ld64-236.3_1+llvm35.darwin_14.x86_64.tbz2" in Mac OS X 10.10

version:1
:debug:clean Attempting ln -sf /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64/work /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/ld64/work
:debug:clean changing euid/egid - current euid: 0 - current egid: 0
:debug:clean egid changed to: 501
:debug:clean euid changed to: 502
:debug:main Executing org.macports.main (ld64)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:archivefetch archivefetch phase started at Wed Oct 22 23:46:49 CEST 2014
:msg:archivefetch --->  Fetching archive for ld64
:debug:archivefetch Executing org.macports.archivefetch (ld64)
:debug:archivefetch euid/egid changed to: 0/0
:debug:archivefetch chowned /opt/local/var/macports/incoming to macports
:debug:archivefetch euid/egid changed to: 502/501
:info:archivefetch --->  ld64-236.3_1+llvm35.darwin_14.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified
:msg:archivefetch --->  Attempting to fetch ld64-236.3_1+llvm35.darwin_14.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/ld64
:msg:archivefetch --->  Attempting to fetch ld64-236.3_1+llvm35.darwin_14.x86_64.tbz2.rmd160 from http://nue.de.packages.macports.org/macports/packages/ld64
:debug:archivefetch The requested URL returned error: 404 Not Found
    while executing
"curl fetch --effective-url effectiveURL --disable-epsv --progress ui_progress_download ${file_url}.rmd160 $signature"
    ("eval" body line 1)
    invoked from within
"eval curl fetch --effective-url effectiveURL $fetch_options {${file_url}.rmd160} {$signature}"
:error:archivefetch org.macports.archivefetch for port ld64 returned: Failed to fetch signature for archive: The requested URL returned error: 404 Not Found
:debug:archivefetch Error code: NONE
:debug:archivefetch Backtrace: Failed to fetch signature for archive: The requested URL returned error: 404 Not Found
    while executing
"portarchivefetch::fetchfiles"
    (procedure "portarchivefetch::archivefetch_main" line 5)
    invoked from within
"portarchivefetch::archivefetch_main org.macports.archivefetch"
    ("eval" body line 1)
    invoked from within
"eval $procedure $targetname"
:info:archivefetch Warning: targets not executed for ld64: org.macports.activate org.macports.archivefetch org.macports.fetch org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install
:error:archivefetch Failed to install ld64
:debug:archivefetch could not read "/opt/local/share/doc/llvm-3.5/html/doxygen.css": no such file or directory
    while executing
"::file type $file"
:notice:archivefetch Please see the log file for port ld64 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64/main.log

Change History (3)

comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Keywords: gcc removed
Port: ld64 added
Priority: HighNormal

There are no binaries for Yosemite yet, so that explains why fetching the signature would fail. What I can't explain is why fetching the archive itself would succeed, since it doesn't exist on our servers.

Please clean ld64 and try again. Also please ensure that your DNS servers function properly; see MisbehavingServers for some common errors we see with broken DNS servers.

If none of that helps, you can install with the -s flag (as in sudo port -s install gcc48); this will instruct MacPorts to not even try to get a binary. Or you can accomplish the same thing by editing macports.conf and telling it to always build from source. You can remove this setting once binaries become available for Yosemite. This is probably still several weeks away and will be announced on the MacPorts mailing lists.

Note that gcc47 and earlier do not work on Yosemite yet; see #43978. Use gcc48 or newer for now.

comment:2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Binaries for Yosemite did in the mean time become available, and gcc47 did get fixed for Yosemite as well. Are you still seeing this problem after running "sudo port selfupdate"?

comment:3 Changed 8 years ago by jmroot (Joshua Root)

Resolution: fixed
Status: newclosed

No response; assuming fixed as per comment:2.

Note: See TracTickets for help on using tickets.