Opened 11 months ago

Closed 6 months ago

#67631 closed defect (fixed)

apple-gcc42 @5666.3: checksum mismatch

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: jeremyhu (Jeremy Huddleston Sequoia)
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: Cc:
Port: apple-gcc42

Description

--->  Fetching distfiles for apple-gcc42
--->  Attempting to fetch gcc-5666.3.tar.gz from http://opensource.apple.com/tarballs/gcc/
--->  Verifying checksums for apple-gcc42                                                    
Error: Checksum (rmd160) mismatch for gcc-5666.3.tar.gz
Error: Checksum (sha256) mismatch for gcc-5666.3.tar.gz
Error: Failed to checksum apple-gcc42: Unable to verify file checksums
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_apple-gcc42/apple-gcc42/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port apple-gcc42 failed

Probably because distfiles from opensource.apple.com, which used to be manually generated and uploaded, now redirect to github automatically-generated tarballs.

Attachments (1)

apple-gcc42.Portfile.patch (1.3 KB) - added by edolnx (Carl Perry) 7 months ago.
Portfile patch which includes new checksum hashes and directory name fix

Download all attachments as: .zip

Change History (4)

Changed 7 months ago by edolnx (Carl Perry)

Attachment: apple-gcc42.Portfile.patch added

Portfile patch which includes new checksum hashes and directory name fix

comment:1 Changed 7 months ago by edolnx (Carl Perry)

I found that the new files have a different prefix because of an error in their generation on GitHub. The extracted directory has an extra gcc- prefix, which I'm accounting for in the post-extract section. This is now building with the bootstrap variant on my G5 Mac running 10.4.11. The diff of my Portsfile to the one in the current repository is attached.

comment:2 Changed 7 months ago by edolnx (Carl Perry)

I found that I needed to do a similar thing to ld64 in #68538 and instead of renaming the directory, I made a symbolic link. I'm unsure which approach is preferred.

comment:3 Changed 6 months ago by jmroot (Joshua Root)

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.