Slashdot Mirror

← Back to Stories (view on slashdot.org)

FreeBSD Removes GCC From Default Base System

Posted by Unknown on from the autoconf-revival dept.

An anonymous reader writes "With the LLVM/Clang migration, FreeBSD developers have now disabled building GCC and the GNU C++ standard library (libstdc++) as part of the FreeBSD base system. GCC and libstdc++ have been superseded by LLVM's Clang and libc++, respectively, on primary architectures for FreeBSD 10.0." You can still flip a few switches to get GCC, but the system compiler will still be clang. Update: 09/11 14:50 GMT by U L : Reader Noryungi noted that the What's Cooking for FreeBSD 10 page is also worth a look, adding "I have to say, this is shaping up to be a very interesting release. Bhyve [the BSD hypervisor], in particular, sounds very promising."

8 of 333 comments (clear)

  1. Oblig, appropriate XKCD by PSVMOrnot · · Score: 5, Funny

    "the system compiler will still be clang"

    Or the Onionequse version: FreeBSD's move to revolutionary new swording system adds a whole new meaning to compiling

  2. More interesting page for FreeBSD 10... by Noryungi · · Score: 5, Interesting

    Try this one: https://wiki.freebsd.org/WhatsNew/FreeBSD10

    I have to say, this is shaping up to be a very interesting release. Bhyve, in particular, sounds very promising...

    --
    The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
    1. Re:More interesting page for FreeBSD 10... by MatthiasF · · Score: 5, Informative

      I think the updates to ZFS are more impressive. The addition of LZ4 compression (50-80% faster), SSD TRIM support and the new NOP-write that reduces the need to write to compressed disks will all mean commodity hardware SANs running FreeBSD will be able to give the big boys a run for their money.

      So, better compression, SSD speed-up and less need to write to changed files, means there will be a huge performance increase.

  3. Re:Just one question by Lendrick · · Score: 5, Informative

    See this link for an explanation:

    http://unix.stackexchange.com/questions/49906/why-is-freebsd-deprecating-gcc-in-favor-of-clang-llvm/49970#49970

    In short, mostly it's due to FreeBSD's issues with the GPL, not all of which are purely philosophical (it affects their funding, for one thing). On the other hand, if you don't have a beef with the GPL, it's probably best to stick with GCC, which produces more performant code.

  4. Re:Just one question by lactose99 · · Score: 5, Informative

    Licensing.

    GCC in the FreeBSD base is stuck at v4.2.1 as that was the last version licensed under the GPLv2. As this is about 7 years old by GCC standards a newer compiler is a welcomed change and since CLANG is BSD-licensed it is more in line with the project's goals anyway.

    --
    Fully licensed blockchain psychiatrist
  5. Re:Just one question by Anonymous Coward · · Score: 5, Funny

    I'd have to agree with the "anti-performant" sentiment. It isn't cromulent to say "performant" if don't want to sound like a douche. It makes it seem like you're trying to embiggen yourself.

  6. Re:Clang is Slower by tlhIngan · · Score: 5, Informative

    No its slower. Phoronix benchmark GCC vs Clang all the time. http://www.phoronix.com/scan.php?page=article&item=llvm_clang33_3way&num=1

    Except FreeBSD is not using GCC 4.8. They're using GCC 4.2.1, the last version that was GPLv2.

    While the current version of GCC may be faster than Clang/LLVM, that doesn't mean Clang/LLVM isn't faster than what is in use now, so the switch may even boost performance compared to the ancient version of GCC in use.

  7. Re:Why? by David+Gerard · · Score: 5, Interesting

    tl;dr Apple is allergic to the GPL v2, and really allergic to the GPL v3. They were never happy about gcc being their base compiler, so they've been funding the hell out of LLVM/Clang so they can use that as their base compiler instead. Apple is also the main backer of FreeBSD.

    --
    http://rocknerd.co.uk