[Mono-list] I give up / Mac OS X PPC support
Thu, 8 Apr 2004 22:07:07 -0700
Sadly, I must agree. The mono team have made excellent progress=
on bringing PPC into the JIT era.... but.....
On a whim, I decided to install fedora core 1 and build mono. It=
built and installed without incident. Truly remarkable. I must=
say that I was impressed. XSP kept crashing, but that is a=
On x86 hardware, I prefer windows xp/2003. Sorry, I love *nix,=
but linux doesn't do much for me on x86, especially when=
x86/windows offers 100% compatibility and killer dev tools.=
Frankly, there is no real reason to host asp.net apps under=
apache, when my XP box does better after locking it down. No=
religion here folks, just reality.
OS/X and PPC is a different story. This is a situation that is=
DYING for an x86 crossover platform. Don't talk to me about=
Java.... if I wanted java, I wouldn't be using mono or c#.
C++/wxWindows/Qt/GTK/etc... yawn. Once again, I want c#.
Mono on the PPC is painful. There is no *documented*, stable or=
official GUI toolkit support. Hell, even the core runtime is=
about as stable as IIS 4. :)
Beyond that, the mono releases are hit and miss. You have about a=
75% chance of the build failing or getting the dreaded 'bus=
I appreciate the new features and the roadmap, but if all mono=
has to offer is x86/linux stability, then mono has only=
succeeded in doing is providing a 'free' implementation of the=
.net runtime that runs on the same commodity hardware that a=
fully supported and commercial version runs on.
Mono cannot win if it sticks to the 'linux vs. windows' card.=
Linux hacks hate MS and C# and .NET. Corporate windows users=
will be reluctant to adopt linux/mono when they can get a fully=
supported, commercial version from MS that will run on the same=
hardware. Believe it or not, most windows shops adopting .NET=
don't care about OS licensing costs or security. They are=
interested in RAD. So mono is a little like selling ice cubes to=
Now, if mono ran reliably on HPUX, sparc, linux, os/x, windows,=
*bsd and some other *nix variants, then you would have succeeded=
in beating MS at their own game. The only argument against .net=
now is that it isn't cross platform. If mono fills that niche,=
then the sky is the limit.
No offense to the mono team, but you should either drop support=
for PPC entirely or actually concentrate on getting it as stable=
Sorry for the long rant guys... its been a long day... :)
Original Message -----------------------
> my problem with gtk# personally is that mac os x is not=
> although you can find people who hacked it together, if you co=
> from cvs, and install it, the samples don't work. i don't have=
> box, only a mac, and i would love to play with mono on it, but=
> been two months now, and i don't feel any closer.
> there are also problems with xsp, and sometimes mono doesn't=
> either (i mean cvs version).
Grudgingly, I have to agree with above statement(s). Mono=
Mac OS X/ PPC is fragile at best. I even tried to put together a=
on the basic steps (
but I have all but given up trying to maintain that page. This=
because mono not reliable from day to day, release to release, on=
PPC / Mac OS X platform.
I am not saying that running off the CVS tree is the most stable=
work, but this goes for the releases also. 0.29 worked on the=
0.30 didn't without some major hacking. 0.31 doesn't work=
Some of the steps I have taken to compile mono include:
- configure switches
- external, 3rd party source downloads
- editing actual code/headers to accommodate the PPC platform.
What's worse, is that when I encounter errors, i receive almost=
on the mailing lists. Some of these are not doubt strange=
some are very common, but my posts go unanswered either way.
I haven't even gotten to gtk#...
Segmentation faults, bus errors, frozen compiles, etc.... The=
goes on and on. I hope to come back to mono in a few months,=
PPC support is better. But for now, I feel that it's a lost=
Mono-list maillist - Monoemail@example.com