Slashdot Mirror


Popular platforms Switched To gcc 3.3.1 on NetBSD

Dan writes "The anticipated GCC3.3.1 switch on NetBSD has happened for some of the popular platforms. NetBSD's Matthew Green announced that he has switched the alpha, i386, sparc and sparc64 ports to use GCC 3.3.1 as the default system compiler. At the same time, NetBSD's Matt Thomas announced that the arm ports(acorn26, acorn32, cats, and shark) have been switched over as well."

26 comments

  1. gcc by Tirel · · Score: 2, Interesting

    Does GCC now properly support -march=athlonxp ? (it was broken in x=3.2)

    1. Re:gcc by noselasd · · Score: 2, Interesting

      Got any pointers to the brokenness ? I use -march=athlon-xp on RedHat 9 (gcc 3.2.2 + some patches) and it seems ok.
      Another point. Will NetBSD 1.6.2(or any 1.6.x) include this switch to gcc 3 ?
      Or is it a feature of the upcoming NetBSD 2.0 ?
      Which leads to; when can one expect NetBSD 2.0 ? This year ? 2005 ?
      (zealots that know nothing more than "when its ready" need not reply.)

    2. Re:gcc by Anonymous Coward · · Score: -1, Flamebait

      When it's ready.

      In the meantime, Linux 2.6 will be out and you can use that. You'll enjoy a better system anyway. ;-)

    3. Re:gcc by Anonymous Coward · · Score: 0

      Ofcourse. The joy of kernel panics, fsckd filesystems, not to menton enjoying the system thrashing around figuring out what to swap out and what not to. (fix that VM mr Torvalds)

    4. Re:gcc by Anonymous Coward · · Score: 0

      probably not. the next version will be 1.6.2 and then 1.7
      the second number is incremented every year, so you have 4 more years to go till 2.0

    5. Re:gcc by Anonymous Coward · · Score: 0

      NetBSD 1.6.x will not be changed to gcc 3.3.x.

      The next major release of NetBSD (2.0) will contain this fix. We hope to start the NetBSD 2.0 release cycle by the end of this year.

  2. Question by wowbagger · · Score: 0, Troll

    So, the next time a *BSDer starts bitching about how the GPL is not "free", does this mean we can point out the hypocrisy of criticizing those who provide you with the single most important tool needed to enjoy the environment of your choice?

    1. Re:Question by kjs3 · · Score: 3, Insightful

      Nice troll. You know...all I ever hear is Stallman and associated syncophants telling people not to use *BSD because it's not "free", at least by their definition. Which is, of course, the only valid one. Hypocracy indeed.

    2. Re:Question by Anonymous Coward · · Score: 2, Insightful

      I have to point out X11 is pretty fundemental for most primarily GPL-based Linux distros too. Currently pure GPL or pure BSD licensed platforms aren't an option.

      One another note, TENDRA *may* present a valid alternative to GCC someday (which would be nice -- I don't care about the license, but diversity is good!). Sadly, I wouldn't advise anyone to hold their breath waiting.

    3. Re:Question by Anonymous Coward · · Score: 0

      Whether it is "free" or not is irrelevant. The fact that *BSD is dying
      should be reason enough to avoid it. No future, my dear.

    4. Re:Question by Anonymous Coward · · Score: 0
      BSD and AIDS

      This just in: homosexuality among *BSD users has skyrocketed. The cause is yet to be determined, however most sources indicate that it has something to do with *BSD users comforting each other in an strictly unusual way, to be quite a frank about it, gay sex. On Monday *BSD was giving a sad prognosis, it was dying. It probably won't have much longer to live. So when news broke out hell broke loose. Jimmy an avid *BSD user had this to say:

      "When I heard this news I was utterly devastated, so I went to my friend Darl, who is also a *BSD user. He didn't yet know of the unfortunate, and he didn't take it well. He broke down in tears, this is the second blow to him in a week, he found out that he contracted AIDS from a Black homosexual prostitute on the street one day. I said to Darl, 'well you know something *BSD is dying, and well, I'm going to die with it.'

      I pulled down my pants and bent over, Darl took care of the rest. I don't know if I have yet to get AIDS, but we have gay anal sex everyday, without any lubricant for maximum ripage. The *BSD mailing list I joined reports the same thing happening among the other *BSD users. We are all planning on having one massive gay orgy on Saturday, so if you want to go out and be with *BSD up in heaven, come join us."

      Well you've heard it folks from a true *BSD user. They have all turned gay because of these unfortunate happenings.
  3. MIPS port? by Anonymous Coward · · Score: 0

    Ummmm? MIPS CPU is not major?

  4. Answer. by Anonymous Coward · · Score: 1, Funny

    Sure, and the next time when someone uses the word "Linux" to mean anything other than the Kernel Tarball as released by Linux Torvalas, can I point out how that is a marketing and branding powergrab taken right from the Mircosoft marketing playbook?

  5. What We Can Learn From BSD by Anonymous Coward · · Score: -1, Offtopic

    What We Can Learn From BSD
    By Chinese Karma Whore, Version 1.0

    Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.

    Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.

    These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.

    As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.

    Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.

    The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureaucratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.

  6. Elegy for *BSD by Anonymous Coward · · Score: -1, Troll

    Elegy For *BSD


    I am a *BSD user
    and I try hard to be brave
    That is a tall order
    *BSD's foot is in the grave.

    I tap at my toy keyboard
    and whistle a happy tune
    but keeping happy's so hard,
    *BSD died so soon.

    Each day I wake and softly sob
    Nightfall finds me crying
    Not only am I a zit faced slob
    but *BSD is dying.

  7. Fact: *BSD is dying by Anonymous Coward · · Score: -1, Flamebait
    We all know that *BSD is dying, it almost goes without saying. Yes, ever hapless *BSD continues to be mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The erosion of user base for FreeBSD continues in a head spinning downward spiral.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major marketing surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among hobbyist dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking.

    Fact: *BSD is dying

  8. *BSD for Windows XP? by Anonymous Coward · · Score: 0
    Is there a version of *BSD that works under WinXP? Please provide a BiTt0rReNt link to the installer. TIA!

    PS It's WinXP Professional, no service packs installed.

    1. Re:*BSD for Windows XP? by noselasd · · Score: 1

      I don't have any bittorrent link , but you can download the install cd from e.g. www.netbsd.org or www.freebsd.org. You will need VMWare to install it under windowsXP though. And you need not worry about the viruses and worms you have on your unpatched winxxp (and your head) will infect the *BSD, the daemon will keep them away.

    2. Re:*BSD for Windows XP? by Anonymous Coward · · Score: 0

      You have been trolled.

  9. *BSD Suxors by Anonymous Coward · · Score: -1, Troll
    In a startling turn of events today, a previously little-known fact came into the public eye: "*BSD Sux0rs". This came as a complete surprise to the BUWLA, or BSD Users With Large Assholes, as they previously thought that *BSD 0wned.

    "You see, even though I have never contributed code to any BSD project, I thought it was my duty to be a big asshole to others which don't use the OS I do, because it just 0wnz.", said one FreeBSD user. "Now that I know it sux0rs, though, I have to go find something else to be an asshole about."

    One notorious OpenBSD fanatic known as WideOpen, told reporters, "I have to kill myself. This isn't how it was supposed to happen. My BSD has always been the best, and shouting that opinion in other people's faces at every chance I got has been my only hobby. It was all I ever did. It was what got me out of bed in the morning. Now I have to die. I will jam my bedpost up my ass until I hit my brain. It is the only way to go: BSD style."

    In the volatile world of operating systems anything can happen. "At least we don't sux0r as much as Windows users", BigAzz, a relatively well-known NetBSD user said. "Screaming things in people's faces is my calling. Now I need to scream that BSD sux0rs. What a sad world. At least I won't kill myself like those uber-asshole OpenBSD guys. They are just way over the top. Or were, at least."

    Nobody knows for sure what the future holds for the state of operating systems, but with Netcraft confirming the sux0r status, *BSD users all over the world will have to stick something else up their asses from now on or risk looking even more gay than they used to.

  10. Does not support VAX by Anonymous Coward · · Score: 0

    I repeat: You cannot use GCC 3.x on the VAX arch.

    1. Re:Does not support VAX by Anonymous Coward · · Score: 0

      You cannot really use g++-2.95 on alpha. You choose.

    2. Re:Does not support VAX by Anonymous Coward · · Score: 0

      GCC 3.x does does not support ELF on VAX... yet.

      NetBSD will have in-tree support for VAX with GCC 3.x "soon", and those changes will be fed back to the GCC mainline.

    3. Re:Does not support VAX by Anonymous Coward · · Score: 0
      Video professor says:

      this Bitch iS Dead
  11. RMS says *BSD is free by yerricde · · Score: 1

    all I ever hear is Stallman and associated syncophants telling people not to use *BSD because it's not "free", at least by their definition.

    The X11 license, the Expat license, and the new BSD license are listed on GNU.org as GPL-compatible free software licenses, and the old BSD license is listed as not compatible with the GNU GPL but still a free software license. Thus, an operating system consisting of Expat licensed programs, X11 licensed programs, and *BSD licensed programs is free software.

    Please show me where Mr. Stallman has discouraged users from making use of non-copylefted free software. In fact, www.gnu.org and www.stallman.org run Apache HTTP Server, whose license resembles the old BSD license, on the Debian GNU/Linux OS.

    --
    Will I retire or break 10K?
  12. Strange bedfellows -- Red Hat Linux and NetBSD 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.