GCC 3.3.1 Switch Coming Soon On NetBSD
Dan writes "Matthew Green says he is ready to switch sparc, sparc64, i386 & alpha ports to using GCC3.3.1 by default on NetBSD. He's uploaded 4 snapshots (one per port ;-), all cross compiled from i386-netbsd. However, there appears to be work involved with fixing approximately 193 broken packages, as reported by NetBSD's Jan Schaumann."
seeing how the non-comatose (though apparently approaching something resembling brain dead) posters can't even tell the difference between "Net" and "Free", I'm not at all surprised that anyone interested in this news is talking about it elsewhere, instead of on slashdot.
Until recently many packages required gcc2.x for compilation simply because 3.x has been relatively untested. Will this bring some kind of instability in NetBSD if say the compilation is successful but with tonnes of warning messages? Are gcc 2.x and 3.x really that different?
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
Dude, you could at least read the story title... This is about NetBSD.
Programming can be fun again. Film at 11.
I'm testing GCC3 and the system is working ok. But the failing packages are really annoying. Missing blackbox...
That's probably because most BSD users have given up on the Slashdot BSD section. The Slashdot BSD section is overrun by trolls and FUD.
BSD is software which can be used freely by anyone. The only way for BSD to die is for people to completely stop using BSD code, but since BSD code is used in so many other software products it really won't ever die.
It's the immaturity of some of these Slahdot readers that have made the Slashdot BSD section go down the drain. But really, you know what's really sad. That these people have nothing esle to do in their poor excuse of a life that they turn to the BSD section to spout out FUD and repeat the "BSD is Dying" troll.
Why do I come here then? Because I too have nothing better to do. Actually, I guess maybe because sometimes through all the trolls and FUD there are some good posts.
Given up? I wouldn't say that. Simply put there isn't anything glamorous happening in the world of BSD from a sensationalist point of view. And lets face it, most of the BSD headlines just aren't that interesting. I mean what is there to say about one of the BSDs moving to GCC 3x?
I am also very pissed that they aren't filtered out.
Lets fight that bullshit!
First I will examine how easy it is to script trollings into the BSD section, perhaps the Slashdot crew does a little bit of defense. But I doubt it somehow.As they don't communicate, I have to find it out myself.
Next thing is to develop a troll scanner to demonstrate how to detect that bullshit. My guess is that those are very easy to detect.
I am not sure what will be the step after that.
Some stupid ideas are:
I don't know yet.It is not easy. Vigilantism is something I don't really want. On the other extreme doing nothing seems only to let the situation deteriorate further.
Or should one simply switch over to Daemon News? This section is cheap rip-off most of the time anyway.
Guess this bot will beg for up mods to do something positive with the karma (auto modding the trolls down?). The source should also kept in an open source repository under BSD license!
BSD BullShitDefense
Wow! BSD is the most fun of dying software. Skilled Anonymous Cowards get to make careful calculations about the number of remaining users, and now BSD even receives poems that rhyme!
It seems that the dead or near-dead, like BSD and Mac OS 9, only seem to get more interesting. Mac OS 9 is almost dead, of course, because it was replaced by Mac OS X, which is BSD-based. But the death of BSD seems to be far more interesting anything else. When Microsoft killed Internet Explorer for the Mac, the only result was a typical, hundreds-of-comments Slashdot article. But Mac is now BSD-based, of course.
I recently repaired Mac OS 9 and added OpenBSD to what had been essentially a GNU/Linux-only system. Interestingly, since BSD is relying on life-support from Linux software, I was able to keep running KDE as usual. Now, when BSD is dying, seems to be the most interesting time to run BSD on a computer.
==========
There are two types of people: those who are in the world, and those who aren't.
I think you mean one MORE BSD moving to 3.x, but yeah its' true what you say. There's really nothing all that exciting going on. But that can be said about the rest of the Open Source world. Nothing is all that exciting anymore. Not KDE, not GNOME, not Linux, etc. It's just the same old shit cooked up in a different way.
Hell, it's almost safe to say that there isn't much exciting going on in the rest of the computing world. Seems like things are moving kinda slow these days. I guess the only thing that I'm looking forward to these days as far as computing is the Athlon64 with a 64bit version of Windows. Why Windows? Because it's quite usable.
But, don't fear. I'll stil use FreeBSD for my servers. It's stable and easy to maintain. That's what I like most about it.
Have you checked out OSNews. Seems to be alot more open minded inteligent people there that actually post decent comments under BSD related news. It's not perfect, but it's a lot better than Slashdot's BSD Section.
Shut up. Or supply something original or funny.
There is an old BSD curse: ``May you run an interesting operating system''.
_O_
.|< The named which can be named is not the true named
That makes for the best sig ever.
It is interesting to note that every NetBSD software, including NetBSD itself, requires a Red Hat product, in fact owes its practical existence to Red Hat GCC.
Yeah, but some of us using VAX systems have discovered that GCC 3.3 DOES NOT WORK on our systems and nobody seems interested in fixing it.
see:
http://mail-index.netbsd.org/port-vax/2003/09/
(remember to take the space out that slashcode puts in)
Dis beatch be one dead ho.
*anything* is better than slashdot.
In fact, I have no friggin idea why I am even writing this response. I shouldn't be here. I gave up on slashdot years ago.
Once you get past the fact that *BSD is fragmented between a myriad of incompatible kernels, there is the historical record of failure and of failed operating systems. *BSD experienced moderate success about 15 years ago in academic circles. Since then it has been in steady decline. We all know *BSD keeps losing market share but why? Is it the problematic personalities of many of the key players? Or is it larger than their troubled personas?
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.