clang in DragonFly, soon

John Marino has added the starting framework to use clang as the alternate base compiler in DragonFly.  Note that it’s not hooked into the build yet.  This is the first non-GCC compiler added into DragonFly, so there’s some work yet before you can have an all-clang system.  This should replace GCC 4.7, which is the current alternate compiler.  GCC 5.0 is the default, if you didn’t know.

Note that clang is present in dports, so it’s already been available for general use, for some time.  This framework is for building DragonFly itself.

Lazy Reading for 2016/03/20

I’m sort of proud of how wide a range of topics are covered this week.

 

In Other BSDs for 2016/03/19

This time, this was all last-minute.

 

Lazy Reading for 2016/03/13

I had too many links for this as early as Tuesday.

Your unrelated video link of the week: Rotoscoped Horse.  Taken from the old Muybridge photos.  (via)

In Other BSDs for 2016/03/12

Has anyone been watching the AsiaBSDCon video?  I have not been awake/unbusy at the right times.

 

Hammer not show

The ‘hammer show’ command can be used to dump the B-Tree structure of a Hammer volume, and CRC errors can be spotted.  It’s rare that anyone would need it, but if you do, this dumped information will include file hierarchy information.

If that makes you a bit nervous to repost any of that information when talking about it in public, Tomohiro Kusumi has added an ‘obfuscate’ option to ‘hammer show’ that does just that – it hides path information from the debug output.

New CPUTYPE variables

John Marino rearranged how GCC5 handles CPUTYPE settings.  If you are specifically setting the target CPU when compiling, his commit will give you an exact list of what to target.

Note that I am not saying another architecture – this is all x86_64.  I also don’t recommend doing this unless you have a specific use for it – compiler overoptimizations often create more problems than they fix.