One method of compile testing WARNS changes on several architectures

Simon L. Nielsen simon at
Mon Sep 13 02:50:15 PDT 2004

On 2004.09.13 12:19:43 +0300, Ruslan Ermilov wrote:

> To test with a minimal time effort, you do this (while in src/):
> $ make toolchain TARGET_ARCH=<arch>
> This step should be repeated for each architecture to be tested
> against.  This will take a lot of time, but an order less than a
> full buildworld.
> $ make _depend everything SUBDIR_OVERRIDER=<bit> TARGET_ARCH=<arch>
> (The underscore before "depend" is intentional.)  <bit> is a part
> of src/ tree that you want to test (can be a list), and <arch>
> should be looped over with each architecture to be tested against.
> Example.  To test if a changed bin/cat still compiles cleanly under
> Alpha and AMD64, e.g. due to you clamping down the WARNS level, you
> do this:
> 1.  Prepare the toolchains:
> make toolchain TARGET_ARCH=alpha
> make toolchain TARGET_ARCH=amd64
> 2.  Test changes:
> make _depend everything SUBDIR_OVERRIDE=bin/cat TARGET_ARCH=alpha
> make _depend everything SUBDIR_OVERRIDE=bin/cat TARGET_ARCH=amd64
> 3.  You can then modify cat's sources/makefile, and repeat step #2.
> P.S.  The syntax for PC98 would be "TARGET_ARCH=i386 TARGET=pc98".

This seems like something that IMO really should be put in some
documentation.  Perhaps the Developers Handbook?  (I can Docbook'ify
it if needed).

Simon L. Nielsen
FreeBSD Documentation Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :

More information about the freebsd-current mailing list