The answer is simply cheap and simple hardware trying to handle data pouring in at Gbit speeds on one side, and sending out at.384Mbit speeds on the other side.
Q: I'm trying to link my binary statically, but it's failing to link because it can't find 'crt0.o.' Why?
A: Static linking of user binaries is not supported on Mac OS X. Tying user binaries to the internal implementation of Mac OS X libraries and interfaces would limit our ability to update and enhance Mac OS X. Instead, dynamic linking is supported (linking against crt1.o automatically instead of looking for crt0.o, for example).
We strongly recommend that you consider the limitations of statically linking very carefully, and consider your customer and their needs, plus the long-term support you will need to provide. Apple provides support and attempts to insure complete compatibility through the published APIs, but cannot insure that compatibility in a statically linked project. Any change to Mac OS X, in a system update, security update, or major revision, may break statically linked code.
If your project absolutely must link statically and need crt0.o, you can get the Csu module from Darwin and try building crt0.o statically. Please bear in mind that you must then clearly specify to your customers the compatibility risks involved in installing a product that relies on statically linked code.
"Neither Microsoft nor Apple can compete at the new price points being plumbed by companies looking to cut costs."
I'm pretty sure the first of those two could compete at a low price point for a VERY long time...
Microsoft could (and possibly will) give away Windows XP for the OLPC to all the developing countries, just to make sure the first OS kids associate with computers is "Windows".
As for the second, Apple needn't compete at the low price point, their money is made on premium computers, not dirt cheap PC's you can pickup at your local supermarket. Even so, Apple's not so unlike Microsoft at the core, Jobs offered OS X for the OLPC too.
Anyway, time will tell who exploits the children of the third world countries for their own agendas.
Slashdot Mirror
Did anyone else read this as:
"a group of 14 law professors posed as a teenage boy to harass another teen online, eventually driving her to suicide"
This could all be explained if they compiled with something silly like ICC
http://www.theinquirer.net/en/inquirer/news/2005/07/13/intel-compiler-nobbles-amd-chips-claim
I'm a GenuineIntel, mod me 47% higher!
5) Not available outside of the US
Even with a fake name and address, they go to extreme measures to stop the poor Aussies from getting their music :'(
Back to the iTunes monopoly I go!
(if you != fed; do s/iTunes/bittorrent/)
I was using an NIA interface so I beat you all :o
Patchcord Adams: "Did you hear why they're using Windows 3000 as a prison guard?"
Fry: "No, why?"
Patchcord Adams: "Cause it always locks up." *honk* *honk*
At last, I'll know what to put in the captcha on rapidshare :o
A certain ISP owner has TCP-IP as the license number for their glider :o
The answer is simply cheap and simple hardware trying to handle data pouring in at Gbit speeds on one side, and sending out at .384Mbit speeds on the other side.
The end result is a LOT of buffering.
If you're lucky enough it'll evolve to fix your crappy editing!
Lifted from http://developer.apple.com/qa/qa2001/qa1118.html because I know no one will RTFA
Q: I'm trying to link my binary statically, but it's failing to link because it can't find 'crt0.o.' Why?
A: Static linking of user binaries is not supported on Mac OS X. Tying user binaries to the internal implementation of Mac OS X libraries and interfaces would limit our ability to update and enhance Mac OS X. Instead, dynamic linking is supported (linking against crt1.o automatically instead of looking for crt0.o, for example).
We strongly recommend that you consider the limitations of statically linking very carefully, and consider your customer and their needs, plus the long-term support you will need to provide. Apple provides support and attempts to insure complete compatibility through the published APIs, but cannot insure that compatibility in a statically linked project. Any change to Mac OS X, in a system update, security update, or major revision, may break statically linked code.
If your project absolutely must link statically and need crt0.o, you can get the Csu module from Darwin and try building crt0.o statically. Please bear in mind that you must then clearly specify to your customers the compatibility risks involved in installing a product that relies on statically linked code.
What did you want, a friggin' parade?
Jeez, give a fruit a break.
"Neither Microsoft nor Apple can compete at the new price points being plumbed by companies looking to cut costs." I'm pretty sure the first of those two could compete at a low price point for a VERY long time... Microsoft could (and possibly will) give away Windows XP for the OLPC to all the developing countries, just to make sure the first OS kids associate with computers is "Windows". As for the second, Apple needn't compete at the low price point, their money is made on premium computers, not dirt cheap PC's you can pickup at your local supermarket. Even so, Apple's not so unlike Microsoft at the core, Jobs offered OS X for the OLPC too. Anyway, time will tell who exploits the children of the third world countries for their own agendas.