#Xcode for mac os x 10.6.8 install
Potentially this may be useful to build something that does not build on 10.6 PPC and then install it into it. gcc10 builds this way, and probably gcc11 will as well. You can build outside Macports for powerpc-apple-darwin10. You can build Macports from source as ppc and configure it pretty much identically as on 10.6 PPC. Good news: you can kinda replicate building for ppc on 10.6.8 natively (via Rosetta). Since ppc64 is not supported on 10.6 (both 10A190 and 10.6.8), I thought there is little to no utility to building universal: instead you can build for ppc32 on all three systems and for ppc64 on 10.5.8 (as this is this only one supporting it). The idea behind the way I’ve maintained this thread’s WikiPost is I want someone who’s new to the project to be able to find exactly what they need, quickly - and to get set up, also quickly - by using the WikiPost alone as their springboard.
#Xcode for mac os x 10.6.8 how to
I want to add an update to that now-outdated portion regarding Xcode, but what will help me is to be able to review the steps which one must follow to know exactly how to update that portion.įor that to happen, I’d like to see a step-by-step guide (found in a new WikiPost, for example) to enable anyone here to repeat the steps on their own and verify its functionality in their Build 10A96 or Build 10A190 setup, using Xcode components from 10A190, 10A222, or other builds.įor now, because no one has posted their own reply of “here’s what I did from a ‘stock’ install of 10A190/10A96 to get x-version of Xcode 3.2 up and running,” there isn’t a particular reply I can point to with a link via the WikiPost. The thing is, I have been taking responsibility for maintaining much of this thread’s WikiPost. It installed and starts.Ī lot on your end (and also ’s end) has happened since that was first posted, and your findings and continued work in that area is also the impetus for encouraging you to create a new WikiPost - one concentrating on Xcode and macports and the numerous tweaks you’ve made to make things work well on Build 10A190. On the other hand, probably Xcode 3.1.4 will also work (excluding System tools). Xcode and tools from 10A190 work as they are, from 10A222 work after minor fixes, it seems that all versions through 10A286 likewise work (if not later). I wonder where a statement in Wiki that “no other Xcode” will work besides the one from 10A96 came from. I have not yet finished testing later Xcode tools from DPs, but I can assure tools from 10A222 work normally (Xcode from 10A190 still needed for ld and gnumake). It is not too hard to make things going, but some things are broken.ħ. No easy tutorial feasible for these right now. Same true for building on 10.6.8 for x86_64+ppc. Building on 10.5.8 for ppc+ppc64 is partly working, but major issues are unresolved. (This is actually easy, just gonna require some extra compilation time if you use G4.)Ħ. Making it work requires two installations of Macports with custom config. mpstats is working, which is important – if we want developers to keep supporting antique OS and exotic configurations, we gotta show they are used. I would love to restore ppc64 support into 10.6, however moving dylibs from 10.5.8 makes OS unbootable.ĥ.
Building for ppc64 is possible, but running ppc64 binaries is not. Despite some claims to the contrary, 10.6 PPC has no support of ppc64. Clang is broken, for all practical purposes.Ĥ. Macports gcc8+ at the moment do not build on 10.6 PPC (or 10.5.8).ģ. Port files need fixes, many of them do, but most of such fixes are trivial.Ģ. Macports on 10.6 PPC works without major problems and most ports build for ppc (many web-related fail, however). I have also not made gcc11 build natively on 10.6 PPC yet.ġ. Probably it makes sense to wait a bit though: right now there are unsolved issues with universal binaries and ppc64 (the latter doesn’t affect 10.6 PPC, as we have it, but has a major impact on 10.5.8). I will have to ask (since he did the initial setup and many fixes) and review my fixes for port files before making them public. I can make it, provided we got a number of people interested to actually do that different from zero LOL
0 kommentar(er)
