[MacPorts] #63090: Cannot build gcc7 on Big Sur

MacPorts noreply at macports.org
Sun Jun 13 18:30:08 UTC 2021


#63090: Cannot build gcc7 on Big Sur
-----------------------+--------------------
  Reporter:  weitzner  |      Owner:  (none)
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:
      Port:  gcc7      |
-----------------------+--------------------

Comment (by kencu):

 The gcc7 port on MacPorts uses the official gcc sources, with minimal
 additional patches:

 https://github.com/macports/macports-
 ports/blob/fe54f1efd433a461af0141b945e794e589398271/lang/gcc7/Portfile#L25


 The Darwin maintainer of gcc upstream has his own repository of gcc fixes
 -- these are additions to the main upstream sources that he either has not
 yet added to the gcc official sources, or has not been able to have added
 to the gcc official sources as the branch is closed to updates.

 He has some fixes in his gcc7 repo that look like they most likely would
 fix the build on BigSur. I have not tried it.

 https://github.com/iains/gcc-7-branch/commits/gcc-7-darwin

 So what you would do is to use his sources instead of the official sources
 in the gcc portfile, get rid (most likely) of our patches, or at least
 look them over, and then try building gcc7/libgcc7 using his sources and
 see if they build.

 Or you could use his sources to generate a patchset that applies on top of
 the official gcc7 sources if you need to sell this idea to your company,
 etc.

 If you are interested, then run the test suite and see if that passes your
 needs for accuracy. If it does, then you are good to go forever -- just
 peg that in your own repo and you have gcc7 on BigSur no matter what
 MacPorts does.

 Or just have your own separate build of gcc7 that you use, and have it
 have nothing to do with MacPorts, if that suits you better.

 If nothing I have written here makes any sense at all to you, then I'm
 afraid you're probably Out Of Luck, as it is not too likely anyone is
 going to do that in MacPorts, although you never know.

-- 
Ticket URL: <https://trac.macports.org/ticket/63090#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list