Port libgcc7 is still broken after rebuilding it more than 3 times

[mfacorcoran]

Hi

I just did a port selfupdate and port upgrade outdated and got the following error:

Error: Port libgcc7 is still broken after rebuilding it more than 3 times.
Error: Please run port -d -y rev-upgrade and use the output to report a bug.
Error: rev-upgrade failed: Port libgcc7 still broken after rebuilding 3 times

the log file is attached below

[mfacorcoran]

libgcc7 failure log file

[ryandesign (Ryan Carsten Schmidt)]

[bb3821d49fd1b22d35c82964e158995eb990bf05/macports-ports]

[rickyzhang82 (Ricky Zhang)]

To maintainer,

Why GCC upgrade so frequent?

First of all, it took long time to build. I don't think I need marginal compiler performance improvement to trade off our time to rebuild the whole gcc6 and gcc7.

Secondly, it is horrible to see the build breaks. Do we test portfile before pushing it? If it has not passed build test, why we push the update in haste?

Sorry about my rant. I just feel pissed after building gcc6 and gcc7 for hours, I only need other package which only takes a minute to build.

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

I am sorry to hear about your recent negative experience.
Recently, the rebuilds of GCC have been due to upgrading libgcc to GCC 8.
This was a significant undertaking.

The reason for this particular problem, however, was that you and I install GCC as a universal port.
We each ran across the same problem, and a rebuild was necessary to fix it.
I would venture to guess that not that many others build GCC with the universal variant, and so the error was not caught earlier.

If build times are a significant issues, may I suggest you set up your MacPorts in such a way as to be able to use ​binary packages.
That way, you can (mostly) just download a prebuilt package.