o add hash operations
o make AES operations useful: split into 3 ops based on key length (specify
aes for AES w/ 128 bit keys, aes192 for 192-bit keys, and aes256 for
256-bit keys
o add -c option to force encrypt->decrypt result to be compared against the
original plaintext (need to compare it against a known good implementation
like openssl)
o change multi-threaded test output to be more meaningingful
o fix default block size selection to consider algorithm's blocking needs
case, "today", which corresponds to 00:00 on the day the run starts.
Remove NO_CPU_CFLAGS and NO_CPU_COPTFLAGS. This should be safe since we
clear the environment and set __MAKE_CONF to /dev/null. NO_CPU_CFLAGS
actually breaks the Alpha release by preventing the inclusion of -mieee
in CFLAGS.
Do not set BUILDNAME as the release/Makefile already constructs a better
one than we do (though I wish there was a way to s/-SNAP/-TINDERBOX/)
wrong when running a release tinderbox as root)
Use the setup's COMMENT field in the subject of the failure report, instead
of just "$branch tinderbox".
Tweak the test setups.
Build LINT on -STABLE now that tinderbox.pl knows how. Also try to build
LINT on powerpc and amd64 (this is a formality as they don't have NOTES
so nothing will be built)
Add two setups for release testing, with plenty of NO* to speed things up.
If the config key was not specified on the command line, try to guess it
from the hostname.
NOCDROM, NODOC and NOPORTS to save time and space, but I may remove
those at a later date so we can use the results to populate a snapshot
server.
Document the --machine option.
Make $arch and $machine default to the correct values for the current
system. This shouldn't make any difference unless you run the
tinderbox on a pc98 machine, since for all other platforms, $arch and
$machine are the same.
Only set kernel-related variables if actually building a kernel or a
release.
Be paranoid and cd to the correct directory in each stage so we're
sure we invoke make(1) in the right place.
To support building LINT on -STABLE, don't try to 'make LINT' unless
NOTES exists, but build LINT if the config file exists even if there
is no NOTES.
should no longer be necessary.
Re-enable Kerberos 5 in the -STABLE tinderbox (incorrectly disabled in
the previous commit)
Prepare for, but do not actually enable, mailing reports to
appropriate FreeBSD mailing lists.
legacy stuff (binutils) depend on this order.
For this to work, provide (and use) specialized versions
of bsd.prog.mk and bsd.lib.mk that include the standard
versions first, then augment CFLAGS, DPADD, LDADD, and
LDFLAGS as necessary, with the legacy stuff.
Tested on: 4.0-RELEASE
is because we populate these directories later, and a subsequent
-DNOCLEAN build may fail. So, we put them in
${WORLDTMP}/build/usr/{include,lib} instead and adjust Makefile.boot.
Again, this works on -stable and -current, but might break older
versions.
Submitted by: ru@
FreeBSD. This method attempts to centralize all the necessary hacks
or work arounds in one of two places in the tree (src/Makefile.inc1
and src/tools/build). We build a small compatibility library
(libbuild.a) as well as selectively installing necessary include
files. We then include this directory when building host binaries.
This removes all the past release compatibilty hacks from various
places in the tree. We still build on tip of stable and current. I
will work with those that want to support more, although I anticipate
it will just work.
Many thanks to ru@, obrien@ and jhb@ for providing valuable input at
various stage of implementation, as well as for working together to
positively effect a change for the better.
the command line to tinderbox.pl)
Build Kerberos V in all setups (this was previously taken care of by
tinderbox.pl).
Tweak the 9ball configuration to make powerpc builds work (with a
little help from a toolchain patch provided by grehan)
Allow the user to specify environment variables on the command line.
Set the correct variables for cross-building.
Don't arbitrarily define MAKE_KERBEROS5 and BOOT_UFS.
looking for ^===> can give quite annoying false positives, especially
when building kernels, so drop it; the context can be inferred from
make's "Stop in /foo/bar/baz" messages anyway.
Also add a case that I'd missed the first time around (which happens
to be the common case, not the exception...)
warning: duplicate script for target "double" ignored
The regression-tests do try to hide that message, but the message does
still appear when using -j (eg: 'make -j5 buildworld'). This changes the
regression-test so the expected warning message will not be seen even
when -j is specified.
Reviewed by: jmallett ru
backout_commit.rb. Tool can be used to automate the
process of backing out either small or large commits based off of
one or more commit messages. The result of the script is a shell
script which can be edited or run as needed. New and dead files
are taken into consideration. See the program's usage statement for
more configuration details. Here's an example usage:
<programlisting>
$ mutt
[find commit message, save to disk as cvsmsg.txt]
$ backout_commit.rb ~/cvsmsg.txt
Backout directory: /usr
Backout script: backout-2003-01-31-14-04.sh
Scanning through cvsmsg.txt...done.
Change to /usr and run this script. Please look through this script and
make changes as necessary. There are commented out commands available
in the script.
Example script usage:
mv backout-2003-01-31-14-04.sh /usr
cd /usr
less backout-2003-01-31-14-04.sh
/bin/sh backout-2003-01-31-14-04.sh
rm -f backout-2003-01-31-14-04.sh
</programlisting>
