On 12 Aug, 08:21, William Stein wrote:
> >> Anyway, it seems like we should do something like print a huge warning
> >> and an interactive "are you sure you want to continue? [yes/no]" if
> >> the
> >> "(Apple Inc. Build )" has < some_arbitrary_number, where the
> >> arbitrary number i
>> Anyway, it seems like we should do something like print a huge warning
>> and an interactive "are you sure you want to continue? [yes/no]" if
>> the
>> "(Apple Inc. Build )" has < some_arbitrary_number, where the
>> arbitrary number is something like say 5470?
>>
>> -- William
>
>
> Yo
William Stein wrote:
> On Tue, Aug 11, 2009 at 9:17 PM, David Kirkby wrote:
>> 2009/8/12 William Stein :
>>> On Tue, Aug 11, 2009 at 7:38 PM, Robert
>>> Bradshaw wrote:
On Aug 11, 2009, at 1:42 PM, Dr. David Kirkby wrote:
> I gather that what gcc works on OS X depends on many things.
On Tue, Aug 11, 2009 at 9:17 PM, David Kirkby wrote:
>
> 2009/8/12 William Stein :
>>
>> On Tue, Aug 11, 2009 at 7:38 PM, Robert
>> Bradshaw wrote:
>>>
>>> On Aug 11, 2009, at 1:42 PM, Dr. David Kirkby wrote:
>>>
I gather that what gcc works on OS X depends on many things. Can
anyone
>>>
2009/8/12 William Stein :
>
> On Tue, Aug 11, 2009 at 7:38 PM, Robert
> Bradshaw wrote:
>>
>> On Aug 11, 2009, at 1:42 PM, Dr. David Kirkby wrote:
>>
>>> I gather that what gcc works on OS X depends on many things. Can
>>> anyone
>>> be precise about exactly what works and what does not? I can do
On Tue, Aug 11, 2009 at 7:38 PM, Robert
Bradshaw wrote:
>
> On Aug 11, 2009, at 1:42 PM, Dr. David Kirkby wrote:
>
>> I gather that what gcc works on OS X depends on many things. Can
>> anyone
>> be precise about exactly what works and what does not? I can do some
>> semi-sensible testing in a con
On Aug 11, 2009, at 1:42 PM, Dr. David Kirkby wrote:
> I gather that what gcc works on OS X depends on many things. Can
> anyone
> be precise about exactly what works and what does not? I can do some
> semi-sensible testing in a configure script if I knew what was wanted,
> but I don't.
>
> I h
