[MacPorts] #57032: mozjs52 @52.6.0, mozjs60 @60.1.0: Target C compiler target CPU (unknown) does not match --target CPU (powerpc)

MacPorts noreply at macports.org
Wed Oct 21 14:45:56 UTC 2020


#57032: mozjs52 @52.6.0, mozjs60 @60.1.0: Target C compiler target CPU (unknown)
does not match --target CPU (powerpc)
-------------------------------+----------------------
  Reporter:  ballapete         |      Owner:  (none)
      Type:  defect            |     Status:  assigned
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.5.3
Resolution:                    |   Keywords:  powerpc
      Port:  mozjs52, mozjs60  |
-------------------------------+----------------------

Comment (by kencu):

 to "peg" a port in MacPorts is easy but not encouraged, so there is not
 one command like "peg" to do it.

 The method is to create a folder that is structured like the ports tree
 folder, add ports in there you want modified from the main macports
 offerings, and then configure MacPorts to check your folder first when
 looking for ports. It takes less than two minutes to do this. The full
 instructions are here <https://guide.macports.org/chunked/development
 .local-repositories.html>.

 I have been doing this for years. Mine is here
 <https://github.com/kencu/LeopardPorts/> for an example of what I'm using.
 You can use that as an idea. Specifically for policykit, my peg is here
 <https://github.com/kencu/LeopardPorts/tree/master/security/policykit>.

 MPorts is much more supportive of older systems than other pkg manafers
 for Mac...a few of us like doing this.

 You'll be able to get your system running many many ports (I have
 thousands installed), but not every port is practical to fix.

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


More information about the macports-tickets mailing list