CVS commit: pkgsrc/doc

["Taylor R Campbell" <riastradh%netbsd.org@localhost>]

Module Name:    pkgsrc
Committed By:   riastradh
Date:           Thu May 16 13:21:22 UTC 2024

Modified Files:
        pkgsrc/doc: HOWTO-use-crosscompile

Log Message:
doc/HOWTO-use-crosscompile: Fix confusing comment in example mk.conf.


To generate a diff of this commit:
cvs rdiff -u -r1.15 -r1.16 pkgsrc/doc/HOWTO-use-crosscompile

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Modified files:

Index: pkgsrc/doc/HOWTO-use-crosscompile
diff -u pkgsrc/doc/HOWTO-use-crosscompile:1.15 pkgsrc/doc/HOWTO-use-crosscompile:1.16
--- pkgsrc/doc/HOWTO-use-crosscompile:1.15      Fri Apr 12 19:57:06 2024
+++ pkgsrc/doc/HOWTO-use-crosscompile   Thu May 16 13:21:22 2024
@@ -1,7 +1,7 @@
 Cross-compilation in pkgsrc (user's guide)              -*- outline -*-
 Taylor R. Campbell <riastradh%NetBSD.org@localhost>
 
-$NetBSD: HOWTO-use-crosscompile,v 1.15 2024/04/12 19:57:06 riastradh Exp $
+$NetBSD: HOWTO-use-crosscompile,v 1.16 2024/05/16 13:21:22 riastradh Exp $
 
 The following steps enable you to build binary packages for a machine
 architecture other than the one you are building on.  For example, you
@@ -34,8 +34,9 @@ running NetBSD 6.1 on amd64.
 
 In addition to whatever else you want in your mk.conf for pkgsrc, add:
 
-   # Cross-compile by default.  (Alternatively, you can cross-build
-   # packages with `make package USE_CROSS_COMPILE=no'.)
+   # Cross-compile by default.  (Alternatively, instead of having this
+   # setting in mk.conf, you can cross-build packages by just running
+   # `make package USE_CROSS_COMPILE=yes'.)
    #
    # Note: This must use `?=' so it doesn't override pkgsrc's internal
    # USE_CROSS_COMPILE=no when recursively building toolchain packages