> On 1 Sep 2024, at 18:18, Andy Miller <camil...@telus.net> wrote:
>
> Thanks for your prompt reply (on a weekend!), Ian.
> But I think we’re missing the point (see red text)…
Nope, not missing the point - fixincludes work in a specific way ( they
restrict the changes to header to the minimal set needed to alter them to work
with the compiler ) - it is not their mission to rewrite headers in some more
generic manner.
>> On Aug 31, 2024, at 11:01 PM, Iain Sandoe <i...@sandoe.co.uk> wrote:
>> 0. Which macOS architecture you are installing on (Arm64 is not supported by
>> upstream yet, but there is a development branch)
>
> MacBook Pro (Retina, 15-inch, Mid 2015)
> 2.8 GHz Quad-Core Intel Core i7
I would expect GCC 14.2 to work perfectly OK on that (I test on a mac mini with
very similar specs).
>> 1. the version of XCode command line tools (or xcode app) you are using to
>> build this.
>
> Xcode-14.0.1
Sometimes Xcode versions are incompatible / buggy when used with GCC.
GCC 14.2 was tested with XCode command line tools 14.3 (which was the most up
to date on the macOS 12 platform)
This is with MacOSX12.3.sdk (which is where the original headers come from).
GCC is maintained on a voluntary basis on several platforms (macOS is one) -
it’s not feasible to support testing every permutation of OS and XCode
the version of macOS tested was 12.7.6 - but I doubt that is materially
different to 12.7.4.
>> 2. the configuration line you used.
>
> Well, you’re not likely to find that helpful, as such “lines” are generated
You said you installed GCC 14.2 - how did you do that?
with what configuration line?
We know that GCC works fine on macOS 12 when installed correctly and using
supported bootstrap tools …
... we cannot help you without information on what was done differently that
would explain what you’re seeing.
Problems cannot be fixed unless they can be reproduced.
If the installation is carried out by some 3rd party script or process, then
the first place to go is to the provider of that.
Similarly, we cannot answer a “how can I uninstall this / not get it used? “
without knowing what the installation looks like.
>> We do not have any control over what the OS headers use - you can file a
>> Feedback with Apple to make queries / observations to them
>> (https://feedbackassistant.apple.com).
>
> But you do have such control over the (very few) headers in
> gcc14/…/14.2.0/include-fixed/ !
> (That was the whole point of my message — see above.)
> One such Gnu-modified header begins thusly…
As noted above that is not the purpose or implementation of fixed includes -
the process is not to alter the OS-provided ones to fit some ‘ideal’ but,
rather to patch the smallest amount to make them work with the compiler.
HTH
Iain
