[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] [PATCH] Remove -no-cpp-precomp flag for OS X
From: |
Jim Ursetto |
Subject: |
Re: [Chicken-hackers] [PATCH] Remove -no-cpp-precomp flag for OS X |
Date: |
Sat, 1 Feb 2014 19:54:08 -0600 |
Builds for me, applied.
FYI, this patch was encoded in iso-8859-1, and had to be converted to UTF-8 to
match the Acknowledgements file.
Jim
On Jan 30, 2014, at 2:35 PM, Peter Bex <address@hidden> wrote:
> Hi all,
>
> This was reported off-list: on OS X, we pass the -no-cpp-precomp option
> to the C compiler to enforce GCC's own preprocessor instead of Apple's
> own preprocessor (which was probably massively broken or incompatible).
> This was added to CHICKEN somewhere in 2003.
>
> This option has been deprecated by Apple (but is accepted and silently
> ignored since XCode 1.1), and reportedly this causes breakage using
> (non-Apple) Macports GCC on OS X 10.6.8 (64-bit, SnowLeopard).
> This is gcc (MacPorts gcc47 4.7.3_3) 4.7.3
>
> Here's a reference from the Mozilla project discussing this same problem:
> https://bugzilla.mozilla.org/show_bug.cgi?id=409224
>
> Considering this option stopped doing anything at all so long ago, I think
> we're safe to remove this as well. The attached patch does that.
> If people decide to use an old OS X release (which isn't supported by
> Apple anymore), they could still override C_COMPILER_OPTIONS.
> I'd appreciate if any OS X users could report whether everything keeps
> working.
>
> Thanks to Jason E. Aten for reporting this bug.
>
> Cheers,
> Peter
> --
> http://www.more-magic.net
> <0001-Remove-obsolete-no-cpp-precomp-flag-for-OS-X-build-t.patch>_______________________________________________
> Chicken-hackers mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/chicken-hackers
- Re: [Chicken-hackers] [PATCH] Remove -no-cpp-precomp flag for OS X,
Jim Ursetto <=