Hi Mike, On 13 Sep 2015, at 21:32, Mike Stump wrote:
> On Sep 12, 2015, at 8:02 AM, Iain Sandoe <iain_san...@mentor.com> wrote: >> OK for trunk? chose this comment carefully : " for something that's essentially a constant for the versions of ld that work with current GCC. " > So, does this work on 10.3? not on its own .. see below. > ppc? ppc64? You modify darwin.h, and that file is used everywhere. yes - for ld64-85.2 xcode 3.1.4 - (10.5) (I believe it's supported by ld64-62.1 XC 2.5 on 10.4) - but that toolchain has some problems building modern GCC (strip etc). > If it really works everywhere, Ok. .. So it works everywhere that has a toolchain that can build current GCC. 10.3's (1.5) xcode has been incapable of building GCC since ~ transition to c++. > If it doesn’t, then it should be in a file that is used only on the systems > that support it. Ok, if you figure it is less than universal and needs to go > some other place. ** if there's any sensible thing that can be done for modern GCC with xc 1.5 or less (which i doubt). I think that the place to over-ride would be in some rs6000/darwin7.h ==== The generic solution (actually, made already but not posted) is that I've made a forward-port of the ppc stuff to current ld64, and also fixed up some issues with cctools.. probably tedious to build that lot on 10.3 - but .. if you want c++11 support on 10.3 (or even to build cc1 using a c++ compiler), the native tools are not going to cut the mustard.... --- In the end, we're going to need to use a fixed set of "binutils" for Darwin it's too difficult to span the ages ... (or drop support for older systems, which I'd rather not do). WDYT? I can revise the patch if you think there's a Better Way to do it. Iain
