<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/Makefile, branch release/13.2.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=release%2F13.2.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=release%2F13.2.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2023-01-31T01:46:18Z</updated>
<entry>
<title>Makefile: Avoid sanitizing PATH on non-FreeBSD systems</title>
<updated>2023-01-31T01:46:18Z</updated>
<author>
<name>Jake Freeland</name>
<email>jfree@FreeBSD.org</email>
</author>
<published>2023-01-19T22:24:44Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=6879fc89425f57880fa327a1c528f657f80cf68e'/>
<id>urn:sha1:6879fc89425f57880fa327a1c528f657f80cf68e</id>
<content type='text'>
Allow the build process to find host binaries during the host-symlinks target when
cross-building on non-FreeBSD systems. Whilst most non-FreeBSD systems have all
the needed tools in /sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin (the final
path added by host-symlinks itself), Homebrew for macOS on Arm defaults to
/opt/homebrew/bin, other more niche systems may also deviate and users may
expect tools in a customised PATH to be picked up, unlike on FreeBSD where we
want to ensure everything comes from base. In particular, (un)xz are needed
from Homebrew on macOS, and thus cannot be found on Arm without this.

Note that non-FreeBSD builds enforce BUILD_WITH_STRICT_TMPPATH, and so the
actual main build steps will still use a sanitised PATH.

Reviewed by:	jrtc27, arichardson
MFC after:	1 week
Differential Revision:	https://reviews.freebsd.org/D37991

(cherry picked from commit 16fbf0191243e7c9dff6615b1424b5d39186b36c)
</content>
</entry>
<entry>
<title>Add list-old-{dirs,files,libs} targets.</title>
<updated>2022-07-13T15:22:24Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2022-01-11T19:38:11Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=e3f9397aea99eabe85e8cfdc8721c0283adb2ec4'/>
<id>urn:sha1:e3f9397aea99eabe85e8cfdc8721c0283adb2ec4</id>
<content type='text'>
These targets generate a raw list of the candidate old files roughly
corresponding to the values of OLD_DIRS, OLD_FILES, and OLD_LIBS.
Currently list-old-files also includes uncompressed manpages in
addition to compressed manpages.

Use these targets in the implementation of check-old-* and
delete-old-* to replace duplicated logic.

Reviewed by:	imp, emaste
Sponsored by:	The University of Cambridge, Google Inc.
Differential Revision:	https://reviews.freebsd.org/D33327

(cherry picked from commit 21baf42c57f080835496c5f4f349e9523d22a956)
</content>
</entry>
<entry>
<title>Fix 'make bmake' top-level bootstrapping.</title>
<updated>2021-12-21T13:44:51Z</updated>
<author>
<name>Bryan Drewery</name>
<email>bdrewery@FreeBSD.org</email>
</author>
<published>2021-03-06T17:45:08Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=5815ac31d9c98098242f6709c7a261481ae300fb'/>
<id>urn:sha1:5815ac31d9c98098242f6709c7a261481ae300fb</id>
<content type='text'>
Fixes:	ee10666327b62
(cherry picked from commit eb8bf6bb4204c302e2329b68c8a930be5d44bc9c)
</content>
</entry>
<entry>
<title>Remove 'make update'.</title>
<updated>2021-10-19T23:53:24Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2021-06-11T21:56:28Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=16aa4787ca5cd9de970090eebfa67502b261d6a6'/>
<id>urn:sha1:16aa4787ca5cd9de970090eebfa67502b261d6a6</id>
<content type='text'>
In the CVS days this used be a wrapper around either CVS or CVSup and
used to support updating src, doc, and ports checkouts.  With the move
to subversion this only supported updating src and was itself a
wrapper around 'svn update'.  With Git, users are probably better off
using appropriate Git commands directly to update without needing an
explicit make target as a wrapper.

Reviewed by:	bcr, imp, emaste
Differential Revision:	https://reviews.freebsd.org/D30736

(cherry picked from commit e290182bcf3895ca659dff111bca6a077c4708b1)
</content>
</entry>
<entry>
<title>Makefile: Fix MAKEOBJDIRPREFIX command-line variable check for bmake</title>
<updated>2021-09-07T12:06:46Z</updated>
<author>
<name>Jessica Clarke</name>
<email>jrtc27@FreeBSD.org</email>
</author>
<published>2021-07-21T01:48:10Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=502fa11ee8ee11529371a1d85703a2be6f94f673'/>
<id>urn:sha1:502fa11ee8ee11529371a1d85703a2be6f94f673</id>
<content type='text'>
Unlike the old fmake, running make FOO=bar when using bmake doesn't put
FOO=bar in .MAKEFLAGS at the top level, it instead just puts FOO in
.MAKEOVERRIDES and the full MAKEFLAGS will be formed for sub-makes.
Moreover, this only applies for sub-makes in rules, so this doesn't
apply to those in shell assignments. This means that the current check
does not catch make MAKEOBJDIRPREFIX=..., only those defined in config
files. Thus we must also check .MAKEOVERRIDES explicitly.

Reviewed by:	sjg
MFC after:	1 week
Differential Revision:	https://reviews.freebsd.org/D31015

(cherry picked from commit d0c737e18454868447f731fe2b10d04f50d9d53b)
</content>
</entry>
<entry>
<title>Rename NO_WERROR -&gt; MK_WERROR=no</title>
<updated>2021-01-07T09:31:03Z</updated>
<author>
<name>Alex Richardson</name>
<email>Alexander.Richardson@cl.cam.ac.uk</email>
</author>
<published>2021-01-06T17:55:06Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=7fa2f2a62f04f095e1e27ad55aa22a8f59b1df8f'/>
<id>urn:sha1:7fa2f2a62f04f095e1e27ad55aa22a8f59b1df8f</id>
<content type='text'>
As suggested in D27598. This also supports MK_WERROR.clang=no and
MK_WERROR.gcc=no to support the existing NO_WERROR.&lt;compiler&gt; uses.

Reviewed By:	brooks
Differential Revision: https://reviews.freebsd.org/D27601
</content>
</entry>
<entry>
<title>Makefile: re-wordsmith the blurb about xtoolchain ports</title>
<updated>2020-11-14T18:06:35Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2020-11-14T18:06:35Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=cf82304d7d5e8d9433d46cbdf2db8c2576b85edd'/>
<id>urn:sha1:cf82304d7d5e8d9433d46cbdf2db8c2576b85edd</id>
<content type='text'>
The new version only includes a specific version once, and uses the one
that's currently advised by tinderbox: -gcc6.

It also advises just installing the pkg, but mentions in a side-note at the
end where to find the source in the ports tree.

Reviewed by:	jrtc27
Suggested by:	jhb (use default from tinderbox)
Differential Revision:	https://reviews.freebsd.org/D26820
</content>
</entry>
<entry>
<title>pkgbase: Add incremental packages</title>
<updated>2020-11-02T18:23:50Z</updated>
<author>
<name>Emmanuel Vadot</name>
<email>manu@FreeBSD.org</email>
</author>
<published>2020-11-02T18:23:50Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0ac8aa55da1cb5e53a9102fd007dd01ee6d17894'/>
<id>urn:sha1:0ac8aa55da1cb5e53a9102fd007dd01ee6d17894</id>
<content type='text'>
This adds a new target update-packages which will create the new packages
compared to the last run.

This is how to use it:
At this point we cut a release
$ make buildworld ...
$ make buildkernel
$ make packages

    There is now a PKG_VERSION directory with latest link pointing to it
    Distribute the packages to server

$ something something that update the source tree
$ make buildworld ...
$ make buildkernel
$ make update-packages
You know have a PKG_VERSION directory in the REPODIR and latest link pointing to it.
In PKG_VERSION dir only the packages which differs from the latest run are
named PKG_VERSION, otherwise the old packages are there.

The process is :
Build the new packages in the PKG_VERSION directory
Compare the internal data with the PKG_VERSION_FROM version. The comparison is done
by checking the internal hash of the packages.
By default PKG_VERSION_FROM is set to what the latest link points to.
If the old and new version matches, we rm the new package and cp the old one.

Differential Revision:	https://reviews.freebsd.org/D25984
</content>
</entry>
<entry>
<title>Makefile: add a small blurb about building with gcc xtoolchain</title>
<updated>2020-10-16T15:16:23Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2020-10-16T15:16:23Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=5f2aaba4532c713f74279f0e83208c97af3a3e69'/>
<id>urn:sha1:5f2aaba4532c713f74279f0e83208c97af3a3e69</id>
<content type='text'>
The key details are to install the appropriate flavor of devel/freebsd-gcc9
and pass CROSS_TOOLCHAIN while building.

Suggested by:	kib
</content>
</entry>
<entry>
<title>Eliminate building LINT makefiles</title>
<updated>2020-10-09T00:27:40Z</updated>
<author>
<name>Warner Losh</name>
<email>imp@FreeBSD.org</email>
</author>
<published>2020-10-09T00:27:40Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=bf0cf8dfba39dc1ff6926526fb74add89d0ed896'/>
<id>urn:sha1:bf0cf8dfba39dc1ff6926526fb74add89d0ed896</id>
<content type='text'>
LINT config files are about to be checked in directly. Eliminate
building them by hand here from NOTES files.

Reviewed by: kevans
Differential Revision: https://reviews.freebsd.org/D26540
</content>
</entry>
</feed>
