[MacPorts] #64229: python27 +universal fails to build for ppc+ppc64 on 10.5.8

[MacPorts]

#64229: python27 +universal fails to build for ppc+ppc64 on 10.5.8
---------------------------+-------------------------------------
  Reporter:  barracuda156  |      Owner:  (none)
      Type:  defect        |     Status:  closed
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.7.1
Resolution:  duplicate     |   Keywords:  PowerPC, Leopard, ppc64
      Port:  python27      |
---------------------------+-------------------------------------

Comment (by barracuda156):

 Replying to [comment:18 kencu]:
 > If you find a file called "portconfigure.tcl" you will see all the logic
 and functions used in there.

 This was super-helpful tip! Yes, now I have found a way to make Macports
 pass -arch ppc64 to compiler, and as you told, it breaks down. The same
 compiler builds the same port for ppc without issues and tricks, and
 completely freaks out when ppc64 passed.

 (Basically 10.6 SDK had ppc64 lacking in portconfigure.tcl, which is why
 even setting build_arch ppc64 in macports.conf had no effect.)

 If 10.6 SDK is the problem, then cross-compiling on Intel Mac with
 powerpc64-apple-darwin10 target against 10.6 SDK will be likewise
 pointless.

 I have two things to clarify here:

 1. Does lack of proper support of ppc64 in 10.6 mean that it won′t run
 ppc64 apps properly (provided they are built against 10.5 SDK)?

 2. If it will run, then is there a "correct" way to move a port built on
 10.5.8 into 10.6 in a way it is recognized by Macports on the latter?
 I recall you manually put some port into verified folder to make it
 install, but here there is no such option, since we blocked binary
 archives. I may perhaps make a shared local archive as described in
 Macports guide, however 10.6 won′t pull binaries compiled for 10.5 from
 there, right? Finally, I know it ''might'' work building a port on 10.5.8
 (without installing) and then moving portions of it into interrupted build
 on 10.6 – that is a bad method, I guess, but it helped me with mpich which
 otherwise persistently failed on 10.6 (however I moved only one library,
 not the whole thing).
 Port pkg is useless – I could not make a port installed from a package
 seen by Macports however tried. This perhaps can be a fallback option – at
 least for R framework. I could build it as 64-bit on 10.5.8, make mpkg and
 install into 10.6, outside of Macports (after all, once built, R is self-
 sufficient).

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