Hi Karl
Thanks for your clarity. :-)
> So ... if you'd accept a patch to avoid $set_cc_for_build on
> new-enough Darwin, I can ask to determine what X is.
That would be fine, thanks. The most complete solution would be good,
but anything to reduce the number of users who encounter this problem
On Nov 6, 2013, at 16:09 , Karl Berry wrote:
> As I understand it again, it is a fact that all versions of Darwin later
> than X are on 64-bit hardware. Therefore, as far as I can see, it is
> not in principle necessary to run the compiler to determine it. And
> this would be good, because con
On Wed, Nov 6, 2013 at 7:09 PM, Karl Berry wrote:
>
> So ... if you'd accept a patch to avoid $set_cc_for_build on new-enough
> Darwin, I can ask to determine what X is.
>
Ben,et al cannot determine if a patch is to be accepted without seeing
the patch first. Submit it then ask if would be accept
