DragonFly 6.4.2 released

[Justin Sherrill]

Someone would have to test newer versions of gcc in DragonFly as the
system compiler, to see if there's a technical issue.

There's 2 working compilers in the system at any time - 8.3 is
default, and gcc-4.7 is still there.  I forget the reason to hold that
specific version; might have been license change?  In any case, CCVER
is the variable to change to pick the active compiler.  You can set it
to something installed from dports and see what you get.

Here's a post from the switch to gcc5 as an example:
https://lists.dragonflybsd.org/pipermail/users/2015-February/207455.html

Changing system compiler forces everyone to rebuild their system and
all ports too, so it's not insignificant.  I know people have talked
about moving to clang and etc too.

On Fri, May 9, 2025 at 9:59 PM Sayed Mohammad Badiezadegan
<mbzadegan at gmail.com> wrote:
>
> Thank you for your update, but why is the GCC version still on 8.3 (released in 2019)? Is there any technical problem with GCC version 13.X?
>
>
>
> On Fri, May 9, 2025 at 6:35 PM Ed M <martinezed0001 at gmail.com> wrote:
>>
>> Cool, thought current snapshots  had replaced formal releases
>>
>> On Fri, May 9, 2025 at 5:19 PM Justin Sherrill <justin at shiningsilence.com> wrote:
>>>
>>> DragonFly 6.4.2 is out - this is another bugfix release.  ISO/IMG files are
>>> available now on dragonflybsd.org and mirrors soon, if not already.
>>>
>>> The release page: https://www.dragonflybsd.org/release64/
>>>
>>> And here's what has changed from 6.4.1 to 6.4.2:
>>>
>>> https://lists.dragonflybsd.org/pipermail/commits/2025-May/923524.html
>>>
>>> To update on an existing install:
>>>
>>> > cd /usr
>>> > make src-create
>>> > (or make src-update if you already have a src directory)
>>> > cd src
>>> > git pull
>>> > make build-all
>>> > make install-all
>>> > make upgrade
>>>
>>> After your next reboot, you can optionally update your rescue system:
>>>
>>> (reboot)
>>> > cd /usr/src
>>> > make initrd