[MacPorts] #64615: qt4-mac fails on 10.6.8 Rosetta: Undefined symbols: __Unwind_Resume

[MacPorts]

#64615: qt4-mac fails on 10.6.8 Rosetta: Undefined symbols: __Unwind_Resume
---------------------------+-------------------------------------------
  Reporter:  barracuda156  |      Owner:  (none)
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.7.1
Resolution:                |   Keywords:  powerpc, snowleopard, rosetta
      Port:  qt4-mac       |
---------------------------+-------------------------------------------

Comment (by barracuda156):

 Replying to [comment:3 kencu]:
 > **HOWEVER** if I recall last summer's explorations, it was not in
 libSystem.dylib on the bootleg 10.6-for-PPC I tried, so perhaps
 barracuda156 is really building on that system and posting here as a
 rosetta question?
 >
 > If not -- if this is truly 10.6.8 rosetta -- well then  I have no idea
 why libSystem.dylib isn't being linked in. Something must be totally
 borked.
 >
 > PS. Symbols also seem to be in the 10.6 SDK:

 @kencu why would I do that? Firstly, I think being honest is not only
 ethical but also beneficial – mutual trust is conducive to cooperation.
 Secondly, if I describe the problem in a wrong way, suggestions to fix it
 will be wrong either.

 As you asked me before, I do not open any tickets for 10.6 PPC problems,
 explicitly or otherwise. If I get a problem on 10.6 PPC, I try building a
 port on 10.5.8 and/or 10.6.8, and if it still fails, open a ticket
 specifying an OS version. If a port actually builds on 10.5.8 and/or
 10.6.8, I can replicate it on 10.6 PPC, and if not, in the worst case pre-
 build it and import into 10.6 PPC. So far the only case which comes to my
 mind is `ux-trie`, which builds on 10.6.8 but not on 10.6 PPC. In other
 cases it is other way round: many ports do build on 10.6 PPC with no
 tweaks but fail on 10.6.8, sometimes fixing those on 10.6.8 is far from
 trivial (example `x265`).
 I do refer to 10.6 PPC at times, and that is done explicitly, for cases
 when something builds on 10.6 PPC but fails on 10.5.8 or/and 10.6.8. And
 surely, my aim of getting involved with 10.6.8 Rosetta is fix building for
 10.6 PPC, which, I believe, I have mentioned earlier, besides of that
 being a common sense: there is no point to build for ppc on 10.6.8 Rosetta
 to use exclusively on 10.6.8 as we have it.

 It might be the case though if a port is addressing content of /Developer
 including SDK folder, that causes some specific issue. I use Xcode 3.2
 (currently the release version from 10A433) on this system and an SDK from
 10A190. The latter I needed to build gcc10ppc and gcc11ppc to install
 those on 10.6 PPC (since so far I was unable to fix building those
 natively: I mentioned a linker problem in Iain’s thread).
 I can swipe SDK back to the stock one or test on another installation of
 10.6.8 where I was building for x86_64 + ppc, I have Xcode 4.2 and stock
 SDK from it there.

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