Re: Bus error on MacOS

[Eric Wing <ewmailing@...>]

On 5/5/13, Coda Highland <chighland@gmail.com> wrote:
> On Sun, May 5, 2013 at 4:28 PM, Jay Carlson <nop@nop.com> wrote:
>> On May 5, 2013, at 6:31 PM, Coda Highland wrote:
>>
>>> On Sun, May 5, 2013 at 3:07 PM, Miles Bader <miles@gnu.org> wrote:
>>>> Owen Shepherd <owen.shepherd@e43.eu> writes:
>>>>> They're moving away from GCC for the same reason the BSDs are: they
>>>>> don't
>>>>> like the GPL3 and refuse to touch it with a barge pole
>>>>
>>>> Apple has been butthurt about the GPL for _ages_, long predating the
>>>> GPL3... if you remember, NeXT was forced to release their objective C
>>>> changes, and they were _not_ happy about it.
>>
>> They also shipped without bash originally.
>>
>>> But the GPLv3 in particular is problematic for a company like Apple,
>>> because while GPLv2 stuff can be used on an iPhone as long as Apple
>>> distributes source, GPLv3 stuff cannot.
>>
>> No, Apple certainly *can* distribute GPLv3-licensed code on any platform.
>> They have decided they don't like the terms offered.
>
> The statements are equivalent. From the perspective of Apple's prior
> behavior, the GPLv3 prohibits Apple's use of it; from the perspective
> of the FSF, Apple doesn't like the terms.
>
> /s/ Adam
>

For the real reason Apple dropped gcc and went to clang, watch
Chandler Carruth's (of Google) "Clang: Defending C++ from Murphy's
Million Monkeys". From minute 2 to minute 6, he quotes Richard
Stallman and demonstrates why gcc was a dead end for them (and all
others like Google).

http://channel9.msdn.com/Events/GoingNative/GoingNative-2012/Clang-Defending-C-from-Murphy-s-Million-Monkeys

-Eric
-- 
Beginning iPhone Games Development
http://playcontrol.net/iphonegamebook/