Slashdot Mirror


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."

46 comments

  1. Re:Two hours into the article... by Anonymous Coward · · Score: 0

    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.

  2. I didnt know gcc3.3 was that mature by mnmn · · Score: 2, Interesting

    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
    1. Re:I didnt know gcc3.3 was that mature by __past__ · · Score: 3, Interesting
      The biggest annoyance is that newer GCCs treat multiline string literals (i.e. strings with embeded newline characters as opposed to \n) as errors, instead of just issuing a warning. This is actually conforming behaviour, so packages should really be fixed upstream. Other than that, I never had any problems beyond simple warnings, but of course, YMMV.

      Given that GCC got better and better in terms of ISO/ANSI C conformance, most problems are probably bugs that just didn't show up yet because they went with a matching GCC bug. So fixing them will only increase conformance, and hence portability to other compilers.

    2. Re:I didnt know gcc3.3 was that mature by JDizzy · · Score: 3, Informative

      Yeah, this is the same issue we had in FreeBSD. Lots of little pendantic issues that used to be a warning become errors. This is, as you point out, an issues with interpritaion of the ANSI C standards. Lots of folks try to say their code works, and it doesn't work due to a bug in the new GCC, but that is just water under the bridge when they figure out that the world has changed, and they have to change their code with it.

      --
      It isn't a lie if you belive it.
    3. Re:I didnt know gcc3.3 was that mature by vesamies · · Score: 3, Informative

      Inline functions in GCC2 are brainded. GCC3 makes this (and many more things I'm sure) work right. It's a shame they used that old compiler for so long, but I guess stabilizing a toolchain for 30+ (?) platforms is not that easy.

    4. Re:I didnt know gcc3.3 was that mature by iamacat · · Score: 1

      Well, it depends on weather the code is really violating the standard or it is, as you say, an interpetation problem. If some part of the standard is not clear to an average programmer and could be interpeted in a certain, useful way, the compiler should try to digest the code rather than showing off author's strict interpetation.

      Also, I hope older versions of standard are supported and system header files can somehow indicate their own version so that the old programs actually compile.

  3. Re:Two hours into the article... by __past__ · · Score: 1

    Dude, you could at least read the story title... This is about NetBSD.

  4. Re:Two hours into the article... by Anonymous Coward · · Score: 0
    advocate_one should re-read his copy of the Linux Advocacy mini-HOWTO, particulary the Canons of Conduct. Lots of good advice in there. For example
    • Focus on what Linux has to offer. There is no need to bash the competition. Linux is a good, solid product that stands on its own.
    • Respect the use of other operating systems. While Linux is a wonderful platform, it does not meet everyone's needs.
  5. blackbox by vesamies · · Score: 1

    I'm testing GCC3 and the system is working ok. But the failing packages are really annoying. Missing blackbox...

  6. Re:It's dead, Jim by bsd_usr · · Score: 4, Insightful

    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.

  7. Re:It's dead, Jim by archen · · Score: 2, Insightful

    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?

  8. Re:It's dead, Jim by BSD+BullShitDefense · · Score: 2, Interesting
    I am fed up with the troll postings.

    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:

    • Harassing the Slashdot editors, by autofiling complaints, after easy bullshit detection until they include a filter in their software?
    • Flooding the other sections in the hope that then the problem will get addressed?
    • Creating a proxy that passes all content through except for identified trollings?
    • Forwarding each BSD troll post to the linux kernel hacker list?

    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

  9. BSD is Rhyming (Re:The *BSD Wailing Song) by ThreeFarthingStone · · Score: 2, Insightful

    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.
  10. Re:It's dead, Jim by bsd_usr · · Score: 2, Interesting

    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.

  11. Re:It's dead, Jim by bsd_usr · · Score: 1

    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.

  12. Re:It's dead, Jim by BSD+BullShitDefense · · Score: 0, Troll

    Shut up. Or supply something original or funny.

  13. Re:It's dead, Jim by R.Caley · · Score: 3, Funny
    And lets face it, most of the BSD headlines just aren't that interesting.

    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
  14. Thanks by Anonymous Coward · · Score: 0

    That makes for the best sig ever.

  15. Red Hat Linux owns GCC by Anonymous Coward · · Score: 0
    Ever since Red Hat bought Cygnus, GCC is in effect a Red Hat Linux product. Most of the significant development on GCC is performed by Red Hat Linux employees. Therefore NetBSD is a [possibly illegitimate] offspring of Red Hat. And of course, GCC is under copyright by our good friends at Richard Stallman's Free Software Foundation (home of GNU).

    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.

  16. It breaks on VAX by Anonymous Coward · · Score: 1, Interesting

    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)

  17. Re:It's dead, Jim by Anonymous Coward · · Score: 0

    Dis beatch be one dead ho.

  18. Re:It's dead, Jim by Anonymous Coward · · Score: 0

    *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.

  19. food for thought by Anonymous Coward · · Score: 0
    When it comes to the subject of operating systems, most of us can agree on at least one thing, and that is the simple plain truth that *BSD is dying. But the deeper question is why? Why did *BSD fail?

    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.