#49589: gcc48 bug --------------------------------+-------------------------------- Reporter: jianguohsiang82@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: duplicate | Keywords: elcapitan Port: gcc48 | --------------------------------+-------------------------------- Changes (by ryandesign@…): * keywords: => elcapitan * status: new => closed * resolution: => duplicate * port: => gcc48 Old description:
I have tried downloading gcc48 several times. Nothing works:
sudo port -f install gcc48
Error: org.macports.build for port gcc48 returned: command execution failed Please see the log file for port gcc48 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/gcc48/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port gcc48 failed
The log file is several pages. I have tried cleaning the port. Nothing works. I first noticed this bug doing a full upgrade after the OS El Capitan update.
New description: I have tried downloading gcc48 several times. Nothing works: {{{ sudo port -f install gcc48 }}} {{{ Error: org.macports.build for port gcc48 returned: command execution failed Please see the log file for port gcc48 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/gcc48/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port gcc48 failed }}} The log file is several pages. I have tried cleaning the port. Nothing works. I first noticed this bug doing a full upgrade after the OS El Capitan update. -- Comment: In the future, please provide the main.log file when you file a ticket. Without it, it's normally impossible for us to know why the build failed. In this case, however, we already know that gcc48 will fail to build for all users running El Capitan. Duplicate of #48471. Note that using the "-f" flag is normally a bad idea. You normally should not use this flag. -- Ticket URL: <https://trac.macports.org/ticket/49589#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X