| #
cd59570c
|
| 02-Mar-2026 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Import tzcode 2026a
|
| #
0d46d875
|
| 11-Dec-2025 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Import tzcode 2025c
|
| #
cc325dd8
|
| 21-Aug-2025 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Import tzcode 2025a
|
| #
18b0e604
|
| 02-Mar-2026 |
Philip Paeps <philip@FreeBSD.org> |
Import tzdata 2026a
|
| #
1eabd3ed
|
| 10-Oct-2025 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
brcm80211: import Broadcom wireless brcmsmac and brcmfmac drivers
This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git e5f0a698b34ed76002dc5cff3804a61c80233a7a ( tag:
brcm80211: import Broadcom wireless brcmsmac and brcmfmac drivers
This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git e5f0a698b34ed76002dc5cff3804a61c80233a7a ( tag: v6.17 ).
show more ...
|
| #
f5eb24d5
|
| 20-Jan-2026 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
rtw89: update Realtek's rtw89 driver
This version is based on git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7 ( tag: v6.19-rc6 ).
|
| #
f73101fa
|
| 06-Feb-2026 |
John Baldwin <jhb@FreeBSD.org> |
universe: Bump default GCC version to 15
Reviewed by: lwhsu, emaste Differential Revision: https://reviews.freebsd.org/D55085
|
| #
94d1731e
|
| 03-Dec-2025 |
Minsoo Choo <minsoochoo0122@proton.me> |
Makefile*: remove powerpcspe
As reported on the freebsd-announce mailing list[1] FreeBSD is continuing to retire 32-bit support. Remove powerpcspe from build infrastructure.
[1] https://lists.free
Makefile*: remove powerpcspe
As reported on the freebsd-announce mailing list[1] FreeBSD is continuing to retire 32-bit support. Remove powerpcspe from build infrastructure.
[1] https://lists.freebsd.org/archives/freebsd-announce/2024-February/000117.html
Signed-off-by: Minsoo Choo <minsoochoo0122@proton.me> Reviewed by: jhibbits, emaste Pull request: https://github.com/freebsd/freebsd-src/pull/1914
show more ...
|
| #
d2f1c8e0
|
| 06-Jan-2026 |
Minsoo Choo <minsoochoo0122@proton.me> |
Makefile: Update doxygen requirements
MFC after: 3 days Reviewed by: imp, ziaee Signed-off-by: Minsoo Choo <minsoochoo0122@proton.me> Closes: https://github.com/freebsd/freebsd-src/pull/1869
|
| #
f7dc7d7a
|
| 08-Oct-2025 |
Lexi Winter <ivy@FreeBSD.org> |
Makefile: Force DISTDIR=/ for (update-)packages
The make(1) variable DISTDIR is used by both ports and src with a different meaning. Some users may set DISTDIR in /etc/make.conf for ports, which pr
Makefile: Force DISTDIR=/ for (update-)packages
The make(1) variable DISTDIR is used by both ports and src with a different meaning. Some users may set DISTDIR in /etc/make.conf for ports, which previously worked fine when building src since the src targets which used this variable were not very commonly used (mainly, make distributeworld).
Unfortunately, with pkgbase becoming the default, this is no longer true since make (update-)packages invokes make stageworld, which is sensitive to DISTDIR, and these users find that their build now fails.
A correct fix for this probably requires renaming one or both of the DISTDIR variables, but for now, work around the problem by setting DISTDIR=/ for the user-facing pkgbase targets, packages and update-package. Since setting DISTDIR doesn't work for these targets anyway, this should not break any existing configurations.
MFC after: 1 week PR: 290010 Reported by: Oleh Vinichenko <moonlapse81@gmail.com> Reviewed by: imp, bapt Sponsored by: https://www.patreon.com/bsdivy Differential Revision: https://reviews.freebsd.org/D52929
show more ...
|
| #
dfc9da62
|
| 03-Oct-2025 |
Lexi Winter <ivy@FreeBSD.org> |
Makefile: Fix ordering for (update-)packages
The (update-)packages targets require buildworld and buildkernel to run first. Add some .ORDER statements to ensure this happens.
This fixes 'make -j8
Makefile: Fix ordering for (update-)packages
The (update-)packages targets require buildworld and buildkernel to run first. Add some .ORDER statements to ensure this happens.
This fixes 'make -j8 buildworld buildkernel packages'.
PR: 289969 Reported by: yasu MFC after: 3 days Reviewed by: yasu, emaste Sponsored by: https://www.patreon.com/bsdivy Differential Revision: https://reviews.freebsd.org/D52877
show more ...
|
| #
4a3fb754
|
| 14-Jul-2025 |
John Baldwin <jhb@FreeBSD.org> |
powerpc: Disconnect 32-bit powerpc from make universe
World and kernels for 32-bit powerpc can still be built using the buildworld and buildkernel targets.
Reviewed by: imp Differential Revision: h
powerpc: Disconnect 32-bit powerpc from make universe
World and kernels for 32-bit powerpc can still be built using the buildworld and buildkernel targets.
Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D51194
show more ...
|
| #
1b06e0b8
|
| 02-Jul-2025 |
Brooks Davis <brooks@FreeBSD.org> |
Revert "src/Makefile: log real/user/system time for build targets"
This broke `make makeman` by unconditionally adding output to all top level targets. Lacking an obvious and trivial workaround, it
Revert "src/Makefile: log real/user/system time for build targets"
This broke `make makeman` by unconditionally adding output to all top level targets. Lacking an obvious and trivial workaround, it makes sense to back it out and rethink.
This reverts commit afa70490ee779646fa0e936801cb28795580bf01.
PR: 287274
Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D51119
show more ...
|
| #
afa70490
|
| 29-Jun-2025 |
Wolfram Schneider <wosch@FreeBSD.org> |
src/Makefile: log real/user/system time for build targets
For some of our build targets such as buildworld, buildkernel etc. we log the real time in seconds how long the build runs. Now we log the u
src/Makefile: log real/user/system time for build targets
For some of our build targets such as buildworld, buildkernel etc. we log the real time in seconds how long the build runs. Now we log the user and system time as well in milliseconds for most build targets.
Example output:
make buildworld [....] >>> Time spent on target buildworld: real 2286.42 user 62870.84 sys 2294.22
PR: 287274
show more ...
|
| #
d4c81623
|
| 03-Mar-2025 |
John Baldwin <jhb@FreeBSD.org> |
universe: Update the default GCC toolchain to GCC 14
Reviewed by: imp, emaste Differential Revision: https://reviews.freebsd.org/D49160
|
| #
697fd847
|
| 29-Jan-2025 |
Jessica Clarke <jrtc27@FreeBSD.org> |
Makefile: Fix several issues with bmake upgrade
Firstly, if NEED_MAKE_UPGRADE isn't set, we shouldn't use whatever bootstrapped bmake happens to be lying around. We're not going to re-run the bmake
Makefile: Fix several issues with bmake upgrade
Firstly, if NEED_MAKE_UPGRADE isn't set, we shouldn't use whatever bootstrapped bmake happens to be lying around. We're not going to re-run the bmake target, so won't make sure it's up-to-date, and thus it could be some ancient unsupported version. We can still, however, optimise setting SUB_MAKE when the file exists, so long as it's guarded by NEED_MAKE_UPGRADE.
Secondly, make kernel-toolchain should also bootstrap bmake if needed, since it's supposed to be the subset of buildworld needed for building a kernel.
Finally, if there is a stale bootstrapped bmake lying around that isn't needed, delete it, since it will only cause confusion, and as far as I can tell nothing else will clean it up, not even cleandir twice. So as to ensure nobody's doing anything crazy with MYMAKE that would cause us to delete something unexpected, or that would change behaviour by no longer checking exists(${MYMAKE}) and using that regardless of version checks, emit an error if the definition in use is not our own.
Reviewed by: emaste, sjg, imp Differential Revision: https://reviews.freebsd.org/D48708
show more ...
|
| #
550137ea
|
| 11-Jan-2025 |
John Baldwin <jhb@FreeBSD.org> |
universe: Permit requesting a specific version of GCC
If USE_GCC_TOOLCHAINS is set to a value matching the pattern 'gcc*', use that as the GCC version. For example, USE_GCC_TOOLCHAINS=gcc16 would u
universe: Permit requesting a specific version of GCC
If USE_GCC_TOOLCHAINS is set to a value matching the pattern 'gcc*', use that as the GCC version. For example, USE_GCC_TOOLCHAINS=gcc16 would use amd64-gcc16 for amd64, etc. If the variable is set to a value that doesn't match that pattern, use the default version.
Reviewed by: imp, emaste Differential Revision: https://reviews.freebsd.org/D48418
show more ...
|
| #
7818c2d3
|
| 12-Jul-2024 |
Andrew Turner <andrew@FreeBSD.org> |
armv6: Remove support for building armv6
With it planned that armv7 will be the only 32-bit kernel when 15.0 is released remove support for armv6.
Remove the top level build infrastructure. It was
armv6: Remove support for building armv6
With it planned that armv7 will be the only 32-bit kernel when 15.0 is released remove support for armv6.
Remove the top level build infrastructure. It was already removed from universe, this just stops it from being built directly.
Reviewed by: mmel, emaste Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D45634
show more ...
|
| #
52e41d1a
|
| 09-May-2024 |
Warner Losh <imp@FreeBSD.org> |
Update example from gcc6 to gcc13
We only "support" gcc12 and gcc13 for cross building, for some value of "support". Update the example from gcc6 to gcc13.
Sponsored by: Netflix
|
| #
49a3780a
|
| 25-Jan-2024 |
Mark Johnston <markj@FreeBSD.org> |
build: Order kernel-toolchain and buildkernel targets
MFC after: 1 week
|
| #
a5ff9005
|
| 26-Jan-2024 |
Emmanuel Vadot <manu@FreeBSD.org> |
pkgbase: Create two new rules for creating repo
This adds two new rules named create-packages-kernel-repo and create-packages-world-repo. The goal of those rules is to create the {kernel,world} pack
pkgbase: Create two new rules for creating repo
This adds two new rules named create-packages-kernel-repo and create-packages-world-repo. The goal of those rules is to create the {kernel,world} packages and after that the repository. It helps a lot for developing with pkgbase by adding the dev machine repository created by those rules on top of the official pkgbase one.
Differential Revision: https://reviews.freebsd.org/D43623 Reviewed by: bapt, emaste Sponsored by: Beckhoff Automation GmbH & Co. KG
show more ...
|
| #
883a1b00
|
| 02-Jan-2024 |
Warner Losh <imp@FreeBSD.org> |
Makefile: Deorbit fmake support
fmake has been out of the tree for 10 years / 5 major releases now. The need to bootstrap from it has been gone for at least 6 if not 8 years. While we may still need
Makefile: Deorbit fmake support
fmake has been out of the tree for 10 years / 5 major releases now. The need to bootstrap from it has been gone for at least 6 if not 8 years. While we may still need to bootstrap bmake, we don't need to do it from fmake, so only retail the infrastructure to update from bmake to bmake. Retain, for now, the WANT_MAKE_VERSION stuff, though we're always up to date when building from supported and quasi-supported platforms.
Also remove all the checks to see if .PARSEDIR is defined. It is always defined and was an early, fail-safe way to tell fmake from bmake during the transition.
Adjust comments that refer to old fmake and remove those no longer relevant.
Sponsored by: Netflix Reviewed by: brooks Pull Request: https://github.com/freebsd/freebsd-src/pull/980
show more ...
|
| #
99b8c0c3
|
| 17-Nov-2023 |
Baptiste Daroussin <bapt@FreeBSD.org> |
pkgbase: create source package
FreeBSD-src for all the sources but the kernel FreeBSD-src-sys just for the kernel
MFC After: 3 days Reviewed by: manu Differential Revision: https://reviews.freebs
pkgbase: create source package
FreeBSD-src for all the sources but the kernel FreeBSD-src-sys just for the kernel
MFC After: 3 days Reviewed by: manu Differential Revision: https://reviews.freebsd.org/D42651
show more ...
|
| #
ecf01a8e
|
| 23-Aug-2023 |
Jessica Clarke <jrtc27@FreeBSD.org> |
Makefile: Support universe-toolchain on non-FreeBSD
We currently pass MACHINE and MACHINE_ARCH as TARGET and TARGET_ARCH respectively for universe-toolchain, but on non-FreeBSD these may not have va
Makefile: Support universe-toolchain on non-FreeBSD
We currently pass MACHINE and MACHINE_ARCH as TARGET and TARGET_ARCH respectively for universe-toolchain, but on non-FreeBSD these may not have values that we understand (e.g. on Linux it will be x86_64 rather than amd64) for TARGET/TARGET_ARCH (note that we do support them for MACHINE/MACHINE_ARCH). Since the choice is a bit arbitrary and merely determines what LLVM's default triple will be, use amd64 on non-FreeBSD as a known-good default.
Reviewed by: jhb Differential Revision: https://reviews.freebsd.org/D41545
show more ...
|
| #
d0b2dbfa
|
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line sh pattern
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|