2013-12-06 12:04:52 +01:00
|
|
|
# $NetBSD: mi,v 1.551 2013/11/12 18:28:36 kefren Exp $
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
#
|
|
|
|
# Note: don't delete entries from here - mark them as "obsolete" instead.
|
|
|
|
#
|
|
|
|
./etc/mtree/set.tests tests-sys-root
|
|
|
|
./usr/libdata/debug/usr/tests tests-base-debug
|
|
|
|
./usr/libdata/debug/usr/tests/atf tests-atf-debug
|
|
|
|
./usr/libdata/debug/usr/tests/atf/atf-c tests-atf-debug
|
|
|
|
./usr/libdata/debug/usr/tests/atf/atf-c++ tests-atf-debug
|
|
|
|
./usr/libdata/debug/usr/tests/atf/atf-c++/detail tests-atf-debug
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/libdata/debug/usr/tests/atf/atf-c/detail tests-atf-debug
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/atf/atf-compile tests-obsolete obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/atf/atf-report tests-atf-tests
|
|
|
|
./usr/libdata/debug/usr/tests/atf/atf-run tests-atf-tests
|
|
|
|
./usr/libdata/debug/usr/tests/atf/formats tests-atf-debug
|
|
|
|
./usr/libdata/debug/usr/tests/atf/test-programs tests-atf-debug
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/libdata/debug/usr/tests/atf/test_programs tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/atf/tools tests-atf-debug obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/atf/units tests-obsolete obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/bin tests-bin-debug
|
|
|
|
./usr/libdata/debug/usr/tests/bin/df tests-bin-debug
|
|
|
|
./usr/libdata/debug/usr/tests/crypto tests-crypto-debug
|
|
|
|
./usr/libdata/debug/usr/tests/crypto/libcrypto tests-crypto-debug
|
|
|
|
./usr/libdata/debug/usr/tests/dev tests-fs-debug
|
|
|
|
./usr/libdata/debug/usr/tests/dev/audio tests-fs-debug
|
|
|
|
./usr/libdata/debug/usr/tests/dev/cgd tests-fs-debug
|
|
|
|
./usr/libdata/debug/usr/tests/dev/cgd/h_img2cgd tests-obsolete obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/dev/md tests-fs-debug
|
|
|
|
./usr/libdata/debug/usr/tests/dev/scsipi tests-fs-debug
|
|
|
|
./usr/libdata/debug/usr/tests/dev/sysmon tests-fs-debug
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/libdata/debug/usr/tests/fs tests-fs-debug
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/fs/ffs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/fifofs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/hfs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/kernfs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/lfs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/msdosfs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/nfs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/nfs/nfsservice tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/nullfs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/psshfs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/ptyfs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/puffs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/puffs/h_dtfs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/tmpfs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/umapfs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/union tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/fs/vfs tests-fs-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/include tests-include-tests
|
|
|
|
./usr/libdata/debug/usr/tests/include/machine tests-include-tests
|
|
|
|
./usr/libdata/debug/usr/tests/include/sys tests-include-tests
|
|
|
|
./usr/libdata/debug/usr/tests/ipf tests-ipf-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kernel tests-kernel-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kernel/kqueue tests-kernel-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kernel/kqueue/read tests-kernel-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kernel/kqueue/write tests-kernel-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kernel/posix_spawn tests-kernel-tests obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/kernel/tty tests-kernel-tests
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/bootstrap tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/cli tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/engine tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/engine/drivers tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/examples tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/integration tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/integration/helpers tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/store tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/utils tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/utils/cmdline tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/utils/config tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/utils/format tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/utils/fs tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/utils/logging tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/utils/process tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/utils/signals tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/utils/sqlite tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-cli/utils/text tests-kyua-tests
|
|
|
|
./usr/libdata/debug/usr/tests/kyua-testers tests-kyua-tests
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/lib tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/csu tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libbluetooth tests-lib-debug
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/libdata/debug/usr/tests/lib/libbpfjit tests-lib-debug
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/lib/libc tests-lib-debug
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/c063 tests-lib-debug
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/db tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/gen tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/gen/posix_spawn tests-kernel-tests
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/getaddrinfo tests-obsolete obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/getaddrinfo/data tests-obsolete obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/getaddrinfo/h_gai tests-obsolete obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/hash tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/ieeefp tests-obsolete obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/inet tests-lib-debug
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/locale tests-lib-debug
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/net tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/net/getaddrinfo tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/regex tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/rpc tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/setjmp tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/ssp tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/stdio tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/stdlib tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/string tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/sys tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/termios tests-lib-debug
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/time tests-lib-debug
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/tls tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libc/ttyio tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libcrypt tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libcurses tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libdes tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libevent tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libexecinfo tests-lib-debug
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/libdata/debug/usr/tests/lib/liblutok tests-lutok-debug
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/lib/libm tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libobjc tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libposix tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libposix/bsd tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libposix/posix1 tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libposix/posix2 tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libppath tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libprop tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libpthread tests-lib-debug
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/libdata/debug/usr/tests/lib/libpthread/dlopen tests-lib-debug
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/lib/librt tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/librumpclient tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/librumphijack tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libskey tests-lib-debug
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/libdata/debug/usr/tests/lib/libsljit tests-lib-debug
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/lib/libtre tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/libutil tests-lib-debug
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/libdata/debug/usr/tests/lib/semaphore tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/lib/semaphore/pthread tests-lib-debug
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/libexec tests-lib-debug
|
|
|
|
./usr/libdata/debug/usr/tests/libexec/ld.elf_so tests-libexec-debug
|
|
|
|
./usr/libdata/debug/usr/tests/libexec/ld.elf_so/h_helper_symver_dso0 tests-libexec-debug
|
|
|
|
./usr/libdata/debug/usr/tests/libexec/ld.elf_so/h_helper_symver_dso1 tests-libexec-debug
|
|
|
|
./usr/libdata/debug/usr/tests/libexec/ld.elf_so/h_helper_symver_dso2 tests-libexec-debug
|
|
|
|
./usr/libdata/debug/usr/tests/modules tests-sys-debug
|
|
|
|
./usr/libdata/debug/usr/tests/net tests-net-debug
|
|
|
|
./usr/libdata/debug/usr/tests/net/bpf tests-net-debug
|
|
|
|
./usr/libdata/debug/usr/tests/net/bpfilter tests-net-debug
|
|
|
|
./usr/libdata/debug/usr/tests/net/carp tests-net-debug
|
|
|
|
./usr/libdata/debug/usr/tests/net/fdpass tests-net-debug
|
|
|
|
./usr/libdata/debug/usr/tests/net/icmp tests-net-debug
|
|
|
|
./usr/libdata/debug/usr/tests/net/if tests-net-debug
|
|
|
|
./usr/libdata/debug/usr/tests/net/if_loop tests-net-debug
|
|
|
|
./usr/libdata/debug/usr/tests/net/net tests-net-debug
|
|
|
|
./usr/libdata/debug/usr/tests/net/sys tests-net-debug
|
|
|
|
./usr/libdata/debug/usr/tests/rump tests-syscall-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/rump/modautoload tests-syscall-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/rump/rumpkern tests-syscall-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/rump/rumpkern/h_client tests-syscall-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/rump/rumpkern/h_server tests-syscall-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/rump/rumpvfs tests-syscall-debug,rump
|
|
|
|
./usr/libdata/debug/usr/tests/sbin tests-sbin-tests
|
|
|
|
./usr/libdata/debug/usr/tests/sbin/resize_ffs tests-sbin-tests
|
|
|
|
./usr/libdata/debug/usr/tests/syscall tests-obsolete obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/usr.bin tests-usr.bin-debug
|
|
|
|
./usr/libdata/debug/usr/tests/usr.bin/id tests-usr.bin-debug
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/libdata/debug/usr/tests/usr.bin/netpgpverify tests-usr.bin-debug
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/libdata/debug/usr/tests/usr.sbin tests-usr.sbin-debug
|
|
|
|
./usr/libdata/debug/usr/tests/util tests-obsolete obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/util/df tests-obsolete obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/util/id tests-obsolete obsolete
|
|
|
|
./usr/libdata/debug/usr/tests/util/systrace tests-obsolete obsolete
|
|
|
|
./usr/tests tests-base-tests
|
|
|
|
./usr/tests/Atffile tests-base-tests
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/Kyuafile tests-base-tests kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf tests-atf-tests
|
|
|
|
./usr/tests/atf/Atffile tests-atf-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/Kyuafile tests-atf-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/atf-c tests-atf-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/atf/atf-c++ tests-atf-tests
|
|
|
|
./usr/tests/atf/atf-c++/Atffile tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/Kyuafile tests-atf-tests atf,kyua
|
|
|
|
./usr/tests/atf/atf-c++/application_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/atf_c++_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/build_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/check_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/config_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/d_include_application_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_atf_c++_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_atffile_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_build_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_check_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_config_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_env_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_exceptions_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_expand_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_formats_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_fs_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_io_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_macros_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_parser_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_process_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_sanity_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_signals_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_tests_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_text_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_ui_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_user_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_include_utils_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/d_use_macros_hpp.cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/detail tests-atf-tests
|
|
|
|
./usr/tests/atf/atf-c++/detail/Atffile tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/detail/Kyuafile tests-atf-tests atf,kyua
|
|
|
|
./usr/tests/atf/atf-c++/detail/application_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/detail/auto_array_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/detail/env_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/detail/exceptions_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/detail/expand_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/detail/fs_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/detail/parser_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/detail/process_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/detail/sanity_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/detail/text_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/detail/ui_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/env_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/exceptions_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/expand_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/fs_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/io_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/macros_hpp_test.cpp tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/macros_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/parser_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/pkg_config_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/process_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/sanity_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/signals_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_application tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_atf_c++ tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_build tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_check tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_config tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_env tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_exceptions tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_expand tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_formats tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_fs tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_io tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_macros tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_parser tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_pkg_config tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_process tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_sanity tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_signals tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_tests tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_text tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_ui tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_user tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/t_utils tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/tests_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/text_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/ui_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/unused_test.cpp tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c++/user_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c++/utils_test tests-atf-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/atf-c/Atffile tests-atf-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/atf-c/Kyuafile tests-atf-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/atf-c/atf_c_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/build_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/check_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/config_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/d_include_atf_c_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_build_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_check_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_config_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_dynstr_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_env_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_error_fwd_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_error_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_expand_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_fs_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_io_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_list_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_macros_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_map_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_object_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_process_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_sanity_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_signals_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_tc_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_tcr_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_text_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_tp_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_ui_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_include_user_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/d_use_macros_h.c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/detail tests-atf-tests
|
|
|
|
./usr/tests/atf/atf-c/detail/Atffile tests-atf-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/atf-c/detail/Kyuafile tests-atf-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/atf-c/detail/dynstr_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/detail/env_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/detail/fs_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/detail/list_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/detail/map_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/detail/process_helpers tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/detail/process_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/detail/sanity_test tests-atf-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/atf-c/detail/test_helpers_test tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/atf-c/detail/text_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/detail/user_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/dynstr_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/env_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/error_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/fs_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/h_check tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/h_processes tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/list_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/macros_h_test.c tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/macros_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/map_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/pkg_config_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/process_helpers tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/process_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/sanity_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_atf_c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_build tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_check tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_config tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_dynstr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_env tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_error tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_expand tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_fs tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_h_lib tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_io tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_list tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_macros tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_map tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_pkg_config tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_process tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_sanity tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_signals tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_tc tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_tcr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_text tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_tp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_ui tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/t_user tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/tc_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/test_helpers_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/text_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/tp_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/unused_test.c tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-c/user_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-c/utils_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-check tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-check/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-check/integration_test tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-check/t_integration tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-cleanup tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-cleanup/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-cleanup/t_integration tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-compile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-compile/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-compile/h_mode tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-compile/t_integration tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-config tests-atf-tests
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/atf-config/Atffile tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-config/Atffile tests-obsolete kyua,obsolete
|
|
|
|
./usr/tests/atf/atf-config/Kyuafile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-config/integration_test tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-config/integration_test tests-obsolete kyua,obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/atf-config/t_integration tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-report tests-atf-tests
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/atf-report/Atffile tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-report/Atffile tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-report/Kyuafile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-report/fail_helper tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-report/fail_helper tests-obsolete obsolete,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/atf-report/h_fail tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-report/h_misc tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-report/h_pass tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-report/h_xfail tests-obsolete obsolete
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/atf-report/integration_test tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-report/integration_test tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-report/misc_helpers tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-report/misc_helpers tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-report/pass_helper tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-report/pass_helper tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-report/reader_test tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-report/reader_test tests-obsolete obsolete,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/atf-report/t_integration tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-run tests-atf-tests
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/atf-run/Atffile tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/Atffile tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-run/Kyuafile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-run/atffile_test tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/atffile_test tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-run/bad_metadata_helper tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/bad_metadata_helper tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-run/config_test tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/config_test tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-run/expect_helpers tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/expect_helpers tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-run/fs_test tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/fs_test tests-obsolete obsolete,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/atf-run/h_bad_metadata tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-run/h_fail tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-run/h_misc tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-run/h_pass tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-run/h_several_tcs tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-run/h_zero_tcs tests-obsolete obsolete
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/atf-run/integration_test tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/integration_test tests-obsolete obsolete,kyua
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/atf/atf-run/io_test tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/io_test tests-obsolete obsolete,kyua
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/atf-run/misc_helpers tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/misc_helpers tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-run/pass_helper tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/pass_helper tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-run/requirements_test tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/requirements_test tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-run/several_tcs_helper tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/several_tcs_helper tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-run/signals_test tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/signals_test tests-obsolete obsolete,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/atf-run/t_config tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-run/t_integration tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-run/t_requirements tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-run/t_test_program tests-obsolete obsolete
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/atf-run/test_program_test tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/test_program_test tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-run/user_test tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/user_test tests-obsolete obsolete,kyua
|
|
|
|
./usr/tests/atf/atf-run/zero_tcs_helper tests-atf-tests atf,!kyua
|
|
|
|
./usr/tests/atf/atf-run/zero_tcs_helper tests-obsolete obsolete,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/atf-sh tests-atf-tests
|
|
|
|
./usr/tests/atf/atf-sh/Atffile tests-atf-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/atf-sh/Kyuafile tests-atf-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/atf-sh/atf-check_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-sh/atf_check_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-sh/config_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-sh/h_misc tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-sh/integration_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-sh/misc_helpers tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-sh/normalize_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-sh/t_atf_check tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-sh/t_config tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-sh/t_integration tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-sh/t_normalize tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-sh/t_tc tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-sh/t_tp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/atf-sh/tc_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/atf-sh/tp_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/data tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/data/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/data/t_pkg_config tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_1 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_1.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_2 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_2.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_3 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_3.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_4 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_4.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_5 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_5.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_50 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_50.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_51 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_51.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_52 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_52.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_53 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_53.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_53.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_54 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_54.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_6 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_atffile_6.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_1 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_1.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_2 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_2.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_3 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_3.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_4 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_4.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_50 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_50.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_51 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_51.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_52 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_52.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_53 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_53.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_53.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_54 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_config_54.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_1 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_1.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_10 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_10.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_11 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_11.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_12 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_12.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_2 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_2.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_3 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_3.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_4 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_4.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_5 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_5.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_6 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_6.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_7 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_7.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_8 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_8.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_9 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_headers_9.experr tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/atf/formats/d_tcr_1 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_1.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_2 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_2.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_3 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_3.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_50 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_50.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_51 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_51.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_52 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_52.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_53 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_53.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_54 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_54.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_60 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_60.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_61 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_61.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_61.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_70 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_70.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_70.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_71 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_71.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_71.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_72 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_72.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_72.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_73 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_73.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_73.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_74 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_74.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_74.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_75 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_75.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_75.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_76 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_76.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_76.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_77 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcr_77.experr tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/formats/d_tcs_1 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_1.errin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_1.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_1.outin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_2 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_2.errin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_2.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_2.outin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_3 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_3.errin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_3.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_3.outin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_4 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_4.errin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_4.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_4.outin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_5 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_5.errin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_5.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_5.outin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_50 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_50.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_51 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_51.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_52 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_52.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_53 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_53.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_53.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_54 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_54.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_54.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_55 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_55.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_55.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_56 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_56.errin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_56.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_56.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_56.outin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_57 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_57.errin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_57.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_57.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tcs_57.outin tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_1 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_1.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_2 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_2.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_3 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_3.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_4 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_4.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_50 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_50.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_51 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_51.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_52 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_52.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_53 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_53.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_54 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_54.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_55 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_55.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_56 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_56.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_57 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_57.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_58 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_58.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_59 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tp_59.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_1 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_1.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_2 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_2.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_3 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_3.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_4 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_4.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_5 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_5.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_50 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_50.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_51 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_51.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_52 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_52.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_53 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_53.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_53.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_54 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_54.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_54.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_55 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_55.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_55.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_56 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_56.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_56.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_57 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_57.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_57.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_58 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_58.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_58.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_59 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_59.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_60 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_60.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_61 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_61.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_62 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_62.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_62.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_63 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_63.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_63.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_64 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_64.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_64.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_65 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_65.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_65.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_66 tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_66.experr tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/d_tps_66.expout tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/h_parser tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/t_parsers tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/formats/t_writers tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/sh_interface tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/sh_interface/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/sh_interface/h_misc tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/sh_interface/t_atf_check tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/sh_interface/t_config tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/sh_interface/t_normalize tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/sh_interface/t_tc tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/sh_interface/t_tp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test-programs tests-atf-tests
|
|
|
|
./usr/tests/atf/test-programs/Atffile tests-atf-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/test-programs/Kyuafile tests-atf-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/test-programs/c_helpers tests-atf-tests atf
|
|
|
|
./usr/tests/atf/test-programs/config_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/test-programs/cpp_helpers tests-atf-tests atf
|
|
|
|
./usr/tests/atf/test-programs/expect_test tests-atf-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/atf/test-programs/fork_test tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/atf/test-programs/meta_data_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/test-programs/result_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/test-programs/sh_helpers tests-atf-tests atf
|
|
|
|
./usr/tests/atf/test-programs/srcdir_test tests-atf-tests atf
|
|
|
|
./usr/tests/atf/test_programs tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test_programs/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test_programs/h_c tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test_programs/h_cpp tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test_programs/h_sh tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test_programs/t_cleanup tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test_programs/t_config tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test_programs/t_env tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test_programs/t_fork tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test_programs/t_meta_data tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test_programs/t_srcdir tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test_programs/t_status tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/test_programs/t_workdir tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/tools tests-atf-tests obsolete
|
|
|
|
./usr/tests/atf/tools/Atffile tests-atf-tests obsolete
|
|
|
|
./usr/tests/atf/tools/h_fail tests-atf-tests obsolete
|
|
|
|
./usr/tests/atf/tools/h_misc tests-atf-tests obsolete
|
|
|
|
./usr/tests/atf/tools/h_mode tests-atf-tests obsolete
|
|
|
|
./usr/tests/atf/tools/h_pass tests-atf-tests obsolete
|
|
|
|
./usr/tests/atf/tools/t_atf_check tests-atf-tests obsolete
|
|
|
|
./usr/tests/atf/tools/t_atf_cleanup tests-atf-tests obsolete
|
|
|
|
./usr/tests/atf/tools/t_atf_compile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/tools/t_atf_config tests-atf-tests obsolete
|
|
|
|
./usr/tests/atf/tools/t_atf_exec tests-atf-tests obsolete
|
|
|
|
./usr/tests/atf/tools/t_atf_killpg tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/tools/t_atf_report tests-atf-tests obsolete
|
|
|
|
./usr/tests/atf/tools/t_atf_run tests-atf-tests obsolete
|
|
|
|
./usr/tests/atf/units tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/t_config tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/t_env tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/t_expand tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/t_fs tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/t_io tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/t_parser tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/t_sanity tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/t_signals tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/t_tests tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/t_text tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/t_user tests-obsolete obsolete
|
|
|
|
./usr/tests/atf/units/t_utils tests-obsolete obsolete
|
|
|
|
./usr/tests/bin tests-bin-tests
|
|
|
|
./usr/tests/bin/Atffile tests-bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/bin/Kyuafile tests-bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/bin/cat tests-bin-tests
|
|
|
|
./usr/tests/bin/cat/Atffile tests-bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/bin/cat/Kyuafile tests-bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/bin/cat/d_align.in tests-bin-tests atf
|
|
|
|
./usr/tests/bin/cat/d_align.out tests-bin-tests atf
|
|
|
|
./usr/tests/bin/cat/t_cat tests-bin-tests atf
|
|
|
|
./usr/tests/bin/cp tests-bin-tests
|
|
|
|
./usr/tests/bin/cp/Atffile tests-bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/bin/cp/Kyuafile tests-bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/bin/cp/t_cp tests-bin-tests atf
|
|
|
|
./usr/tests/bin/dd tests-bin-tests
|
|
|
|
./usr/tests/bin/dd/Atffile tests-bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/bin/dd/Kyuafile tests-bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/bin/dd/t_dd tests-bin-tests atf
|
|
|
|
./usr/tests/bin/df tests-bin-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/bin/df/Atffile tests-bin-tests atf
|
|
|
|
./usr/tests/bin/df/Kyuafile tests-bin-tests atf,kyua
|
|
|
|
./usr/tests/bin/df/h_df tests-bin-tests atf
|
|
|
|
./usr/tests/bin/df/t_df tests-bin-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/bin/expr tests-bin-tests
|
|
|
|
./usr/tests/bin/expr/Atffile tests-bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/bin/expr/Kyuafile tests-bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/bin/expr/t_expr tests-bin-tests atf
|
|
|
|
./usr/tests/bin/pax tests-bin-tests
|
|
|
|
./usr/tests/bin/pax/Atffile tests-bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/bin/pax/Kyuafile tests-bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/bin/pax/t_pax tests-bin-tests atf
|
|
|
|
./usr/tests/bin/ps tests-bin-tests
|
|
|
|
./usr/tests/bin/ps/Atffile tests-bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/bin/ps/Kyuafile tests-bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/bin/ps/keywords tests-bin-tests atf
|
|
|
|
./usr/tests/bin/ps/t_ps tests-bin-tests atf
|
|
|
|
./usr/tests/bin/sh tests-bin-tests
|
|
|
|
./usr/tests/bin/sh/Atffile tests-bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/bin/sh/Kyuafile tests-bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/bin/sh/t_compexit tests-bin-tests atf
|
|
|
|
./usr/tests/bin/sh/t_evaltested tests-bin-tests atf
|
|
|
|
./usr/tests/bin/sh/t_exit tests-bin-tests atf
|
|
|
|
./usr/tests/bin/sh/t_expand tests-bin-tests atf
|
|
|
|
./usr/tests/bin/sh/t_fsplit tests-bin-tests atf
|
|
|
|
./usr/tests/bin/sh/t_here tests-bin-tests atf
|
|
|
|
./usr/tests/bin/sh/t_set_e tests-bin-tests atf
|
|
|
|
./usr/tests/bin/sh/t_ulimit tests-bin-tests atf
|
|
|
|
./usr/tests/bin/sh/t_varquote tests-bin-tests atf
|
|
|
|
./usr/tests/bin/sh/t_wait tests-bin-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/bin/sleep tests-bin-tests
|
|
|
|
./usr/tests/bin/sleep/Atffile tests-bin-tests atf
|
|
|
|
./usr/tests/bin/sleep/Kyuafile tests-bin-tests atf,kyua
|
|
|
|
./usr/tests/bin/sleep/t_sleep tests-bin-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/bin/tar tests-bin-tests
|
|
|
|
./usr/tests/bin/tar/Atffile tests-bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/bin/tar/Kyuafile tests-bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/bin/tar/t_tar tests-bin-tests atf
|
|
|
|
./usr/tests/crypto tests-crypto-tests
|
|
|
|
./usr/tests/crypto/libcrypto tests-crypto-tests
|
|
|
|
./usr/tests/crypto/libcrypto/Atffile tests-crypto-tests crypto
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/crypto/libcrypto/Kyuafile tests-crypto-tests crypto,kyua
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/crypto/libcrypto/d_client.pem tests-crypto-tests crypto
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/crypto/libcrypto/d_conf.out tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/d_conf_ssleay.cnf tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/d_server.pem tests-crypto-tests crypto
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/crypto/libcrypto/evptests.txt tests-crypto-tests crypto
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/crypto/libcrypto/h_bftest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_bntest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_casttest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_conftest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_destest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_dhtest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_divtest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_dsatest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_ecdhtest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_ecdsatest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_ectest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_enginetest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_evp_test tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_exptest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_hmactest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_ideatest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_lhashtest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_md2test tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_md4test tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_md5test tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_mdc2test tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_randtest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_rc2test tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_rc4test tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_rc5test tests-crypto-tests crypto_rc5,crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_ripemdtest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_rsatest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_sha1test tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_shatest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_srptest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_threadstest tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/h_x509v3test tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/t_certs tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/t_ciphers tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/t_hashes tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/t_libcrypto tests-crypto-tests crypto
|
|
|
|
./usr/tests/crypto/libcrypto/t_pubkey tests-crypto-tests crypto
|
|
|
|
./usr/tests/dev tests-fs-tests
|
|
|
|
./usr/tests/dev/Atffile tests-fs-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/dev/Kyuafile tests-fs-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/dev/audio tests-fs-tests
|
|
|
|
./usr/tests/dev/audio/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/dev/audio/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/dev/audio/h_pad tests-fs-tests atf,rump
|
|
|
|
./usr/tests/dev/audio/t_pad tests-fs-tests atf,rump
|
|
|
|
./usr/tests/dev/audio/t_pad_output.bz2.uue tests-fs-tests atf,rump
|
|
|
|
./usr/tests/dev/cgd tests-fs-tests
|
|
|
|
./usr/tests/dev/cgd/Atffile tests-fs-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/dev/cgd/Kyuafile tests-fs-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/dev/cgd/h_img2cgd tests-obsolete obsolete
|
|
|
|
./usr/tests/dev/cgd/h_img2cgd/cgd.conf tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/dev/cgd/h_img2cgd/h_img2cgd tests-obsolete obsolete
|
|
|
|
./usr/tests/dev/cgd/paramsfile tests-fs-tests atf
|
|
|
|
./usr/tests/dev/cgd/t_cgd tests-fs-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/dev/md tests-fs-tests
|
|
|
|
./usr/tests/dev/md/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/dev/md/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/dev/md/h_mdserv tests-fs-tests atf,rump
|
|
|
|
./usr/tests/dev/md/t_md tests-fs-tests atf,rump
|
|
|
|
./usr/tests/dev/raidframe tests-fs-tests
|
|
|
|
./usr/tests/dev/raidframe/Atffile tests-fs-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/dev/raidframe/Kyuafile tests-fs-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/dev/raidframe/t_raid tests-fs-tests atf
|
|
|
|
./usr/tests/dev/scsipi tests-fs-tests
|
|
|
|
./usr/tests/dev/scsipi/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/dev/scsipi/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/dev/scsipi/t_cd tests-fs-tests atf,rump
|
|
|
|
./usr/tests/dev/sysmon tests-fs-tests
|
|
|
|
./usr/tests/dev/sysmon/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/dev/sysmon/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/dev/sysmon/t_swsensor tests-fs-tests atf,rump
|
|
|
|
./usr/tests/dev/sysmon/t_swwdog tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/examples tests-obsolete obsolete
|
|
|
|
./usr/tests/examples/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/examples/t_asm tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs tests-fs-tests
|
|
|
|
./usr/tests/fs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/ffs tests-fs-tests
|
|
|
|
./usr/tests/fs/ffs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/ffs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/ffs/h_ffs_server tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/h_quota2_server tests-obsolete obsolete
|
|
|
|
./usr/tests/fs/ffs/h_quota2_tests tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/rump_edquota tests-obsolete obsolete
|
|
|
|
./usr/tests/fs/ffs/rump_quota tests-obsolete obsolete
|
|
|
|
./usr/tests/fs/ffs/rump_quotactl tests-obsolete obsolete
|
|
|
|
./usr/tests/fs/ffs/rump_repquota tests-obsolete obsolete
|
|
|
|
./usr/tests/fs/ffs/t_clearquota tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/t_fifos tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/t_getquota tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/t_miscquota tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/t_mount tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/t_quota2_1 tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/t_quota2_remount tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/t_quotalimit tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/t_renamerace tests-obsolete obsolete
|
|
|
|
./usr/tests/fs/ffs/t_setquota tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/t_snapshot tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/t_snapshot_log tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ffs/t_snapshot_v2 tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/fifofs tests-fs-tests
|
|
|
|
./usr/tests/fs/fifofs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/fifofs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/fifofs/t_fifo tests-fs-tests atf,rump
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/fs/h_funcs.subr tests-fs-tests atf,rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/hfs tests-fs-tests
|
|
|
|
./usr/tests/fs/hfs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/hfs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/hfs/colon.hfs.bz2.uue tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/hfs/t_pathconvert tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/kernfs tests-fs-tests
|
|
|
|
./usr/tests/fs/kernfs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/kernfs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/kernfs/t_basic tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/lfs tests-fs-tests
|
|
|
|
./usr/tests/fs/lfs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/lfs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/lfs/t_pr tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/msdosfs tests-fs-tests
|
|
|
|
./usr/tests/fs/msdosfs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/msdosfs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/msdosfs/t_snapshot tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/nfs tests-fs-tests
|
|
|
|
./usr/tests/fs/nfs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/nfs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/nfs/nfsservice tests-fs-tests
|
|
|
|
./usr/tests/fs/nfs/nfsservice/exports tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/nfs/nfsservice/rumpnfsd tests-fs-tests atf,rump
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/fs/nfs/t_mountd tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/nfs/t_rquotad tests-fs-tests atf,rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/nullfs tests-fs-tests
|
|
|
|
./usr/tests/fs/nullfs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/nullfs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/nullfs/t_basic tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/psshfs tests-fs-tests
|
|
|
|
./usr/tests/fs/psshfs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/psshfs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/psshfs/h_have_puffs tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/psshfs/ssh_config.in tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/psshfs/ssh_host_key tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/psshfs/ssh_host_key.pub tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/psshfs/sshd_config.in tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/psshfs/t_psshfs tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/ptyfs tests-fs-tests
|
|
|
|
./usr/tests/fs/ptyfs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/ptyfs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/ptyfs/t_nullpts tests-fs-tests atf,rump
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/fs/ptyfs/t_ptyfs tests-fs-tests atf,rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/puffs tests-fs-tests
|
|
|
|
./usr/tests/fs/puffs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/puffs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/puffs/h_dtfs tests-fs-tests
|
|
|
|
./usr/tests/fs/puffs/h_dtfs/h_dtfs tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/puffs/h_have_puffs tests-obsolete obsolete
|
|
|
|
./usr/tests/fs/puffs/ssh_config.in tests-obsolete obsolete
|
|
|
|
./usr/tests/fs/puffs/ssh_host_key tests-obsolete obsolete
|
|
|
|
./usr/tests/fs/puffs/ssh_host_key.pub tests-obsolete obsolete
|
|
|
|
./usr/tests/fs/puffs/sshd_config.in tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/fs/puffs/t_basic tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/puffs/t_fuzz tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/puffs/t_io tests-fs-tests atf,rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/puffs/t_psshfs tests-obsolete obsolete
|
|
|
|
./usr/tests/fs/tmpfs tests-fs-tests
|
|
|
|
./usr/tests/fs/tmpfs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/tmpfs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/tmpfs/h_funcs.subr tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/h_tools tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_create tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_devices tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_dots tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_exec tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_id_gen tests-obsolete obsolete
|
|
|
|
./usr/tests/fs/tmpfs/t_link tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_mkdir tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_mknod tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_mount tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_pipes tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_read_write tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_readdir tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_remove tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_rename tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_renamerace tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_rmdir tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_setattr tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_sizes tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_sockets tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_statvfs tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_symlink tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_times tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_trail_slash tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_truncate tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_vnd tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/tmpfs/t_vnode_leak tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/umapfs tests-fs-tests
|
|
|
|
./usr/tests/fs/umapfs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/umapfs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/umapfs/t_basic tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/union tests-fs-tests
|
|
|
|
./usr/tests/fs/union/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/union/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/union/t_basic tests-obsolete obsolete,rump
|
|
|
|
./usr/tests/fs/union/t_pr tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/vfs tests-fs-tests
|
|
|
|
./usr/tests/fs/vfs/Atffile tests-fs-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/vfs/Kyuafile tests-fs-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/vfs/t_full tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/vfs/t_io tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/vfs/t_renamerace tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/vfs/t_rmdirrace tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/vfs/t_ro tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/vfs/t_union tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/vfs/t_unpriv tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/vfs/t_vfsops tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/vfs/t_vnops tests-fs-tests atf,rump
|
|
|
|
./usr/tests/fs/zfs tests-fs-tests
|
|
|
|
./usr/tests/fs/zfs/Atffile tests-fs-tests atf,zfs,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/fs/zfs/Kyuafile tests-fs-tests atf,zfs,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/fs/zfs/t_zpool tests-fs-tests atf,zfs,rump
|
|
|
|
./usr/tests/games tests-games-tests
|
|
|
|
./usr/tests/games/Atffile tests-games-tests
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/games/Kyuafile tests-games-tests kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/games/t_factor tests-games-tests
|
|
|
|
./usr/tests/include tests-include-tests
|
|
|
|
./usr/tests/include/Atffile tests-include-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/include/Kyuafile tests-include-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/include/d_bitstring_27.out tests-include-tests atf
|
|
|
|
./usr/tests/include/d_bitstring_32.out tests-include-tests atf
|
|
|
|
./usr/tests/include/d_bitstring_49.out tests-include-tests atf
|
|
|
|
./usr/tests/include/d_bitstring_64.out tests-include-tests atf
|
|
|
|
./usr/tests/include/d_bitstring_67.out tests-include-tests atf
|
|
|
|
./usr/tests/include/d_bitstring_8.out tests-include-tests atf
|
|
|
|
./usr/tests/include/machine tests-include-tests
|
|
|
|
./usr/tests/include/machine/Atffile tests-include-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/include/machine/Kyuafile tests-include-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/include/machine/t_bswap tests-include-tests atf
|
|
|
|
./usr/tests/include/sys tests-include-tests
|
|
|
|
./usr/tests/include/sys/Atffile tests-include-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/include/sys/Kyuafile tests-include-tests atf,kyua
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/include/sys/t_bitops tests-include-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/include/sys/t_bootblock tests-include-tests atf
|
|
|
|
./usr/tests/include/sys/t_cdefs tests-include-tests atf
|
|
|
|
./usr/tests/include/sys/t_socket tests-include-tests atf,rump
|
|
|
|
./usr/tests/include/sys/t_tree tests-include-tests atf
|
|
|
|
./usr/tests/include/sys/t_types tests-include-tests atf
|
|
|
|
./usr/tests/include/t_bitstring tests-include-tests atf
|
|
|
|
./usr/tests/include/t_bswap tests-obsolete obsolete
|
|
|
|
./usr/tests/include/t_errno tests-include-tests atf
|
|
|
|
./usr/tests/include/t_glob tests-include-tests atf
|
|
|
|
./usr/tests/include/t_inttypes tests-include-tests atf
|
|
|
|
./usr/tests/include/t_limits tests-include-tests atf
|
|
|
|
./usr/tests/include/t_netdb tests-include-tests atf
|
|
|
|
./usr/tests/include/t_paths tests-include-tests atf
|
|
|
|
./usr/tests/include/t_stdint tests-include-tests atf
|
|
|
|
./usr/tests/include/t_types tests-obsolete obsolete
|
|
|
|
./usr/tests/ipf tests-ipf-tests
|
|
|
|
./usr/tests/ipf/Atffile tests-ipf-tests ipfilter
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/ipf/Kyuafile tests-ipf-tests ipfilter,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/ipf/expected tests-ipf-tests
|
|
|
|
./usr/tests/ipf/expected/bpf-f1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/bpf1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f10 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f11 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f12 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f13 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f14 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f15 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f16 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f17 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f18 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f19 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f20 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f21 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f22 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f24 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f25 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f26 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f27 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f28 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f29 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f30 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f8 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/f9 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i10 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i11 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i12 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i13 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i14 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i15 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i16 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i17 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i18 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i19.dist tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i20 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i21 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i22 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i23 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i8 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/i9 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/in1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/in100 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/in101 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/in102 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/in2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/in3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/in4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/in5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/in6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/in7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ip1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ip2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ip3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ipv6.1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ipv6.2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ipv6.3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ipv6.4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ipv6.5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ipv6.6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/l1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/l1.b tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n10 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n100 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n101 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n102 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n103 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n104 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n105 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n106 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n11 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n11_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n12 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n12_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n13 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n13_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n14 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n14_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n15 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n15_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n16 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n17 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n18 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n1_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n200 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n201 tests-obsolete obsolete
|
|
|
|
./usr/tests/ipf/expected/n202 tests-obsolete obsolete
|
|
|
|
./usr/tests/ipf/expected/n2_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n4_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n5_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n6_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n7_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n8 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n8_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n9 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/n9_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni10 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni11 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni12 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni13 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni14 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni15 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni16 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni17 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni18 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni19 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni20 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni21 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni23 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni8 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/ni9 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/p1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/p10 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/p11 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/p12 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/p13 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/p2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/p3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/p4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/p5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/p6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/p7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/expected/p9 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input tests-ipf-tests
|
|
|
|
./usr/tests/ipf/input/f1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f10 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f11 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f12 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f13 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f14 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f15 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f16 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f17 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f18 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f19 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f20 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f21 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f22 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f24 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f25 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f26 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f27 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f28 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f29 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f30 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f8 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/f9 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ip2.data tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ipv6.1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ipv6.2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ipv6.3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ipv6.4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ipv6.5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ipv6.6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/l1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n10 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n100 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n101 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n102 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n103 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n104 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n105 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n106 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n10_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n11 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n11_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n12 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n12_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n13 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n13_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n14 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n14_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n15 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n15_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n16 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n17 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n17_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n18 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n1_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n200 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n201 tests-obsolete obsolete
|
|
|
|
./usr/tests/ipf/input/n202 tests-obsolete obsolete
|
|
|
|
./usr/tests/ipf/input/n2_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n4_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n5_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n6_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n7_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n8 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n8_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n9 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/n9_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni10 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni11 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni12 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni13 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni14 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni15 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni16 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni17 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni18 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni19 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni20 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni21 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni23 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni8 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/ni9 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/p1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/p10 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/p11 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/p12 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/p13 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/p2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/p3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/p4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/p5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/p6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/p7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/input/p9 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress tests-ipf-tests
|
|
|
|
./usr/tests/ipf/regress/bpf-f1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/bpf1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f10 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f11 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f12 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f13 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f14 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f15 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f16 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f17 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f18 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f19 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f20 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f21 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f22 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f24 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f25 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f26 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f27 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f28.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f28.pool tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f29.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f29.pool tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f30 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f8 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/f9 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i10 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i11 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i12 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i13 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i14 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i15 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i16 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i17 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i18 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i19 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i20 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i21 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i22 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i23 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i8 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/i9 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/in1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/in100 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/in101 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/in102 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/in2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/in3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/in4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/in5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/in6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/in7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ip1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ip2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ip3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ipv6.1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ipv6.2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ipv6.3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ipv6.4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ipv6.5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ipv6.6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/l1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n1 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n10 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n100 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n101 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n102 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n103 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n104 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n105 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n106 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n10_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n11 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n11_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n12 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n12_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n13 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n13_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n14 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n14_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n15 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n15_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n16 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n16_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n17 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n17_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n18 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n1_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n2 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n200 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n201 tests-obsolete obsolete
|
|
|
|
./usr/tests/ipf/regress/n202 tests-obsolete obsolete
|
|
|
|
./usr/tests/ipf/regress/n2_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n3 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n4 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n4_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n5 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n5_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n6_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n7 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n7_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n8 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n8_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n9 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/n9_6 tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni1.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni1.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni10.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni10.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni11.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni11.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni12.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni12.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni13.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni13.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni14.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni14.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni15.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni15.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni16.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni16.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni17.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni17.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni18.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni18.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni19.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni19.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni2.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni2.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni20.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni20.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni21.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni21.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni23.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni23.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni3.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni3.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni4.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni4.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni5.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni5.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni6.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni6.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni7.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni7.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni8.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni8.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni9.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/ni9.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p1.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p1.pool tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p10.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p10.pool tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p11.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p11.pool tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p12.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p12.pool tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p13.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p13.pool tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p2.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p3.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p3.pool tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p4.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p4.pool tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p5.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p5.pool tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p6.ipf tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p6.pool tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p6.whois tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p7.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p7.pool tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p9.nat tests-ipf-tests ipfilter
|
|
|
|
./usr/tests/ipf/regress/p9.pool tests-ipf-tests ipfilter
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/ipf/t_bpf tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/ipf/t_filter_exec tests-ipf-tests atf,ipfilter
|
|
|
|
./usr/tests/ipf/t_filter_parse tests-ipf-tests atf,ipfilter
|
|
|
|
./usr/tests/ipf/t_ipf tests-obsolete obsolete
|
|
|
|
./usr/tests/ipf/t_logging tests-ipf-tests atf,ipfilter
|
|
|
|
./usr/tests/ipf/t_nat_exec tests-ipf-tests atf,ipfilter
|
|
|
|
./usr/tests/ipf/t_nat_ipf_exec tests-ipf-tests atf,ipfilter
|
|
|
|
./usr/tests/ipf/t_nat_parse tests-ipf-tests atf,ipfilter
|
|
|
|
./usr/tests/ipf/t_pools tests-ipf-tests atf,ipfilter
|
|
|
|
./usr/tests/kernel tests-kernel-tests
|
|
|
|
./usr/tests/kernel/kqueue tests-kernel-tests
|
|
|
|
./usr/tests/kernel/kqueue/read tests-kernel-tests
|
|
|
|
./usr/tests/kernel/kqueue/write tests-kernel-tests
|
|
|
|
./usr/tests/kernel/posix_spawn tests-kernel-tests obsolete
|
|
|
|
./usr/tests/kernel/posix_spawn/Atffile tests-kernel-tests obsolete
|
|
|
|
./usr/tests/kernel/posix_spawn/h_fileactions tests-kernel-tests obsolete
|
|
|
|
./usr/tests/kernel/posix_spawn/h_nonexec tests-kernel-tests obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/kernel/posix_spawn/h_spawn tests-kernel-tests obsolete
|
|
|
|
./usr/tests/kernel/posix_spawn/h_spawnattr tests-kernel-tests obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/kernel/posix_spawn/h_zero tests-kernel-tests obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/kernel/posix_spawn/t_fileactions tests-kernel-tests obsolete
|
|
|
|
./usr/tests/kernel/posix_spawn/t_spawn tests-kernel-tests obsolete
|
|
|
|
./usr/tests/kernel/posix_spawn/t_spawnattr tests-kernel-tests obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/kernel/t_extattrctl tests-kernel-tests atf,rump
|
|
|
|
./usr/tests/kernel/t_filedesc tests-kernel-tests atf,rump
|
|
|
|
./usr/tests/kernel/t_lwpctl tests-obsolete obsolete
|
|
|
|
./usr/tests/kernel/t_mkdir tests-obsolete obsolete
|
|
|
|
./usr/tests/kernel/t_pipe tests-obsolete obsolete
|
|
|
|
./usr/tests/kernel/t_poll3w tests-obsolete obsolete
|
|
|
|
./usr/tests/kernel/t_pollts tests-obsolete obsolete
|
|
|
|
./usr/tests/kernel/t_posix_fadvise tests-obsolete obsolete
|
|
|
|
./usr/tests/kernel/t_rnd tests-kernel-tests atf,rump
|
|
|
|
./usr/tests/kernel/t_sigaction tests-obsolete obsolete
|
|
|
|
./usr/tests/kernel/t_time tests-obsolete obsolete
|
|
|
|
./usr/tests/kernel/t_ucontext tests-obsolete obsolete
|
|
|
|
./usr/tests/kernel/t_writev tests-obsolete obsolete
|
|
|
|
./usr/tests/kernel/tty tests-kernel-tests
|
|
|
|
./usr/tests/kernel/tty/Atffile tests-kernel-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/kernel/tty/Kyuafile tests-kernel-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/kernel/tty/t_pr tests-kernel-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/kyua-atf-compat tests-kyua-tests
|
|
|
|
./usr/tests/kyua-atf-compat/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-atf-compat/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-atf-compat/atf-report_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-atf-compat/atf-run_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-atf-compat/atf2kyua_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-atf-compat/helpers tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/bootstrap tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/bootstrap/atf_helpers tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/bootstrap/plain_helpers tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/bootstrap/testsuite tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/cli/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/cmd_about_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/cmd_config_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/cmd_db_exec_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/cmd_db_migrate_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/cmd_debug_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/cmd_help_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/cmd_list_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/cmd_report_html_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/cmd_report_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/cmd_test_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/common_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/config_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/cli/main_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/engine/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/action_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/config_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/context_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/drivers tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/engine/drivers/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/drivers/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/drivers/debug_test_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/drivers/list_tests_helpers tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/drivers/list_tests_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/drivers/run_tests_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/drivers/scan_action_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/exceptions_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/filters_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/kyuafile_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/metadata_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/test_case_atf_helpers tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/test_case_plain_helpers tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/test_case_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/test_program_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/test_result_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/engine/testers_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/examples tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/examples/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/examples/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/examples/syntax_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/integration/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/cmd_about_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/cmd_config_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/cmd_db_exec_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/cmd_db_migrate_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/cmd_debug_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/cmd_help_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/cmd_list_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/cmd_report_html_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/cmd_report_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/cmd_test_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/global_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/helpers tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/integration/helpers/bad_test_program tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/helpers/bogus_test_cases tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/helpers/config tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/helpers/expect_all_pass tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/helpers/expect_some_fail tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/helpers/interrupts tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/helpers/metadata tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/helpers/simple_all_pass tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/integration/helpers/simple_some_fail tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/store tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/store/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/store/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/store/backend_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/store/dbtypes_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/store/exceptions_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/store/metadata_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/store/schema_inttest tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/store/schema_v1.sql tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/store/testdata_v1.sql tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/store/testdata_v2.sql tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/store/transaction_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/utils/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/auto_array_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/cmdline tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/utils/cmdline/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/cmdline/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/cmdline/base_command_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/cmdline/commands_map_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/cmdline/exceptions_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/cmdline/globals_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/cmdline/options_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/cmdline/parser_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/cmdline/ui_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/config tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/utils/config/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/config/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/config/exceptions_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/config/keys_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/config/lua_module_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/config/nodes_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/config/parser_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/config/tree_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/datetime_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/env_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/format tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/utils/format/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/format/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/format/exceptions_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/format/formatter_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/fs tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/utils/fs/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/fs/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/fs/auto_cleaners_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/fs/exceptions_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/fs/lua_module_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/fs/path_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/logging tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/utils/logging/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/logging/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/logging/macros_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/logging/operations_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/memory_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/optional_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/passwd_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/process tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/utils/process/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/process/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/process/child_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/process/exceptions_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/process/fdstream_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/process/helpers tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/process/status_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/process/systembuf_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/sanity_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/signals tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/utils/signals/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/signals/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/signals/exceptions_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/signals/interrupts_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/signals/misc_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/signals/programmer_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/sqlite tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/utils/sqlite/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/sqlite/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/sqlite/c_gate_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/sqlite/database_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/sqlite/exceptions_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/sqlite/statement_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/sqlite/transaction_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/stream_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/text tests-kyua-tests
|
|
|
|
./usr/tests/kyua-cli/utils/text/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/text/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/text/exceptions_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/text/operations_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/text/table_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/text/templates_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-cli/utils/units_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers tests-kyua-tests
|
|
|
|
./usr/tests/kyua-testers/Atffile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/Kyuafile tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/atf_helpers tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/atf_inttest tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/atf_list_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/atf_result_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/cli_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/env_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/error_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/plain_helpers tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/plain_inttest tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/result_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/run_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/stacktrace_helper tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/stacktrace_test tests-kyua-tests atf,kyua
|
|
|
|
./usr/tests/kyua-testers/text_test tests-kyua-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib tests-lib-tests
|
|
|
|
./usr/tests/lib/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/csu tests-lib-tests
|
|
|
|
./usr/tests/lib/csu/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/csu/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/csu/h_initfini tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/csu/h_initfini1 tests-lib-tests atf
|
|
|
|
./usr/tests/lib/csu/h_initfini2 tests-lib-tests atf
|
|
|
|
./usr/tests/lib/csu/h_initfini3 tests-lib-tests atf
|
|
|
|
./usr/tests/lib/csu/t_crt0 tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libbluetooth tests-lib-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libbpfjit tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libbpfjit/Atffile tests-lib-tests atf,sljit
|
|
|
|
./usr/tests/lib/libbpfjit/Kyuafile tests-lib-tests atf,sljit,kyua
|
|
|
|
./usr/tests/lib/libbpfjit/t_bpfjit tests-lib-tests atf,sljit
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libc/Kyuafile tests-lib-tests atf,kyua
|
|
|
|
./usr/tests/lib/libc/c063 tests-lib-tests
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/db tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/db/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libc/db/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/db/README tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/db/h_db tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/db/t_db tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/gen tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/gen/posix_spawn tests-kernel-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/gen/t_glob_star tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/gen/t_ldexp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/gen/t_rbstress tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/gen/t_syslog_pthread tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/getaddrinfo tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data/basics_v4.exp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data/basics_v4v6.exp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data/no_host_v4.exp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data/no_host_v4v6.exp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data/no_serv_v4.exp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data/no_serv_v4v6.exp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data/scoped.exp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data/sock_raw_v4.exp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data/sock_raw_v4v6.exp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data/spec_fam_v4.exp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data/spec_fam_v4v6.exp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/data/unsup_fam.exp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/h_gai tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/getaddrinfo/t_getaddrinfo tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/h_atexit tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/h_nsd_recurse tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/h_protoent tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/h_servent tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/hash tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/hash/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libc/hash/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/hash/data tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/hash/data/md5test-in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/hash/data/md5test-out tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/hash/data/sha1test-in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/hash/data/sha1test-out tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/hash/data/sha1test2-out tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/hash/h_hash tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/hash/t_hash tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/hash/t_sha2 tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/ieeefp tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/ieeefp/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/ieeefp/t_except tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/ieeefp/t_nan_inf tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/ieeefp/t_round tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/ieeefp/t_subnormal tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/inet tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/inet/Atffile tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/inet/Kyuafile tests-lib-tests atf,kyua
|
|
|
|
./usr/tests/lib/libc/inet/t_inet_network tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/locale tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/locale/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libc/locale/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/locale/t_ctype1 tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/locale/t_ctype2 tests-obsolete obsolete
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libc/locale/t_io tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/locale/t_mbrtowc tests-lib-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/locale/t_mbsnrtowcs tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/locale/t_mbstowcs tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/locale/t_mbtowc tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/locale/t_wcscspn tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/locale/t_wcspbrk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/locale/t_wcsspn tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/locale/t_wcstod tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/locale/t_wctomb tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/net tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/net/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libc/net/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/net/getaddrinfo tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/net/getaddrinfo/data tests-lib-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/net/h_hostent tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/net/h_protoent tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/net/h_servent tests-lib-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/net/hosts tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/net/t_getprotoent tests-lib-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/net/t_hostent tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/net/t_nsdispatch tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/net/t_protoent tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/net/t_servent tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/regex/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libc/regex/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/regex/data tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/regex/data/README tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/anchor.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/backref.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/basic.dat tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/basic.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/bracket.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/c_comments.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/categorization.dat tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/complex.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/error.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/forcedassoc.dat tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/leftassoc.dat tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/meta.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/nospec.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/nul.in tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/regex/data/nullsubexpr.dat tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/paren.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/regress.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/repet_bounded.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/repet_multi.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/repet_ordinary.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/repetition.dat tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/rightassoc.dat tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/startend.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/subexp.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/subtle.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/word_bound.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/data/zero.in tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/h_regex tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/h_regex_att tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/regex/t_exhaust tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/t_regex tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/regex/t_regex_att tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/rpc tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/setjmp tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/ssp tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/stdio tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/stdio/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libc/stdio/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/stdio/t_clearerr tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdio/t_fflush tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdio/t_fmemopen tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdio/t_fopen tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdio/t_format tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/stdio/t_fputc tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdio/t_mktemp tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/stdio/t_popen tests-lib-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/stdio/t_printf tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/stdio/t_scanf tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/stdlib/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libc/stdlib/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/stdlib/h_atexit tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/h_getopt tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/h_getopt_long tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/t_abs tests-lib-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/stdlib/t_atexit tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/stdlib/t_atoi tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/t_div tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/t_environment tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/stdlib/t_environment_pth tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/stdlib/t_exit tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/t_getenv tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/t_getopt tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/t_hsearch tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/t_mi_vector_hash tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/t_random tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/t_strtod tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/t_strtol tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/stdlib/t_strtox tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/stdlib/t_system tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/string/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libc/string/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/string/t_memchr tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_memcpy tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_memmem tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_memset tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_popcount tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_strcat tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_strchr tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_strcmp tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_strcpy tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_strcspn tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_strerror tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_stresep tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_string tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/string/t_strlen tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_strpbrk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_strrchr tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_strspn tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/string/t_swab tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/sys tests-lib-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/sys/t_bitops tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/sys/t_cerror tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/sys/t_context tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/sys/t_posix_fadvise tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/libc/sys/t_sigtimedwait_pr_47625 tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/t_atexit tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/t_cdb tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/t_cerror tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/t_clone tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/t_context tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/t_convfp tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/t_gdtoa tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/t_hsearch tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/t_inet tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/t_mktime tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/t_nsdispatch tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/t_protoent tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/t_ptm tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/t_randomid tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/t_servent tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libc/t_strptime tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/termios tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/termios/Atffile tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/termios/Kyuafile tests-lib-tests atf,kyua
|
|
|
|
./usr/tests/lib/libc/termios/t_tcsetpgrp tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libc/time tests-lib-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libc/time/Atffile tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/time/Kyuafile tests-lib-tests atf,kyua
|
|
|
|
./usr/tests/lib/libc/time/t_mktime tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/time/t_strptime tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libc/tls tests-lib-tests
|
|
|
|
./usr/tests/lib/libc/ttyio tests-lib-tests
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libcrypt tests-lib-tests
|
|
|
|
./usr/tests/lib/libcrypt/Atffile tests-lib-tests
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libcrypt/Kyuafile tests-lib-tests kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libcrypt/t_crypt tests-lib-tests
|
|
|
|
./usr/tests/lib/libcurses tests-lib-tests
|
|
|
|
./usr/tests/lib/libcurses/.terminfo.db tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/libcurses/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libcurses/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libcurses/check_files tests-lib-tests
|
|
|
|
./usr/tests/lib/libcurses/check_files/addch.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/addchstr.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/addstr.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/attributes.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/background1.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/background2.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/background3.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/background4.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/background5.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/bell.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/box_standout.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/chgat1.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/chgat2.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/chgat3.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/clear1.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/clear10.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/clear2.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/clear3.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/clear4.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/clear5.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/clear6.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/clear7.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/clear8.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/clear9.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/color_blank_draw.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/color_blue_back.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/color_default.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/color_red_fore.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/color_set.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/color_start.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin1.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin10.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin11.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin12.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin13.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin14.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin2.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin3.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin4.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin5.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin6.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin7.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin8.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/copywin9.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/curs_set1.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/curs_set2.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/curs_set3.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/curses_start.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/fill.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/home.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/timeout.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/wborder.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/wborder_refresh.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/wgetstr.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/wgetstr_refresh.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/window.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/wprintw_refresh.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/wscrl1.chk tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/check_files/wscrl2.chk tests-lib-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libcurses/director tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libcurses/slave tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/t_curses tests-lib-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libcurses/terminfo.cdb tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/terminfo.db tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libcurses/tests tests-lib-tests
|
|
|
|
./usr/tests/lib/libcurses/tests/addch tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/addchnstr tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/addchstr tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/addnstr tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/addstr tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/assume_default_colors tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/attributes tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/background tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/beep tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/box tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/can_change_color tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/cbreak tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/chgat tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/clear tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/color_content tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/color_set tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/copywin tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/curs_set tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/fill_screen tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/getch tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/getstr tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/mvwin tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/start tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/start_color tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/std_defines tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/termattrs tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/timeout tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/wborder tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/window tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/window_create tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/wprintw tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libcurses/tests/wscrl tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libdes tests-lib-tests
|
|
|
|
./usr/tests/lib/libdes/Atffile tests-lib-tests atf,crypto
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libdes/Kyuafile tests-lib-tests atf,crypto,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libdes/t_des tests-lib-tests atf,crypto
|
|
|
|
./usr/tests/lib/libevent tests-lib-tests
|
|
|
|
./usr/tests/lib/libexecinfo tests-lib-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libexecinfo/Atffile tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libexecinfo/Kyuafile tests-lib-tests atf,kyua
|
|
|
|
./usr/tests/lib/libexecinfo/t_backtrace tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/liblutok tests-lutok-tests
|
|
|
|
./usr/tests/lib/liblutok/Atffile tests-lutok-tests atf,kyua
|
|
|
|
./usr/tests/lib/liblutok/Kyuafile tests-lutok-tests atf,kyua
|
|
|
|
./usr/tests/lib/liblutok/c_gate_test tests-lutok-tests atf,kyua
|
|
|
|
./usr/tests/lib/liblutok/debug_test tests-lutok-tests atf,kyua
|
|
|
|
./usr/tests/lib/liblutok/exceptions_test tests-lutok-tests atf,kyua
|
|
|
|
./usr/tests/lib/liblutok/operations_test tests-lutok-tests atf,kyua
|
|
|
|
./usr/tests/lib/liblutok/stack_cleaner_test tests-lutok-tests atf,kyua
|
|
|
|
./usr/tests/lib/liblutok/state_test tests-lutok-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libm tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libm/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libm/t_acos tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_asin tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_atan tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_cbrt tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_ceil tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_cos tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_cosh tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_erf tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_exp tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_floor tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libm/t_fmod tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libm/t_infinity tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_ldexp tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_libm tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libm/t_log tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libm/t_pow tests-lib-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libm/t_precision tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libm/t_round tests-lib-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libm/t_scalbn tests-lib-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libm/t_sin tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_sinh tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_sqrt tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_tan tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libm/t_tanh tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libobjc tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libposix tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libposix/bsd tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libposix/posix1 tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libposix/posix2 tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libppath tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libprop tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libprop/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libprop/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libprop/t_basic tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libpthread tests-lib-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libpthread/dlopen tests-lib-tests
|
|
|
|
./usr/tests/lib/libpthread/t_status tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/librt tests-lib-tests atf
|
|
|
|
./usr/tests/lib/librumpclient tests-lib-tests atf
|
|
|
|
./usr/tests/lib/librumpclient/Atffile tests-lib-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/librumpclient/Kyuafile tests-lib-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/librumpclient/h_exec tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumpclient/h_execthr tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumpclient/h_ution tests-obsolete obsolete
|
|
|
|
./usr/tests/lib/librumpclient/t_exec tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumpclient/t_fd tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack tests-lib-tests atf
|
|
|
|
./usr/tests/lib/librumphijack/Atffile tests-lib-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/librumphijack/Kyuafile tests-lib-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/librumphijack/h_client tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack/h_cwd tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack/h_netget tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack/index.html tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack/netstat.expout tests-lib-tests atf,rump
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/librumphijack/ssh_config.in tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack/ssh_host_key tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack/ssh_host_key.pub tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack/sshd_config.in tests-lib-tests atf,rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/librumphijack/t_asyncio tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack/t_config tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack/t_cwd tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack/t_sh tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack/t_tcpip tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/librumphijack/t_vfs tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/libskey tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libskey/Atffile tests-lib-tests atf,skey
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libskey/Kyuafile tests-lib-tests atf,skey,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libskey/t_algorithms tests-lib-tests atf,skey
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libsljit tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libsljit/Atffile tests-lib-tests atf,sljit
|
|
|
|
./usr/tests/lib/libsljit/Kyuafile tests-lib-tests atf,sljit,kyua
|
|
|
|
./usr/tests/lib/libsljit/h_sljit tests-lib-tests atf,sljit
|
|
|
|
./usr/tests/lib/libsljit/t_sljit tests-lib-tests atf,sljit
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libtre tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libtre/data tests-lib-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/libtre/h_regex_att tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libutil tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libutil/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/lib/libutil/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/lib/libutil/t_efun tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libutil/t_pidfile tests-lib-tests atf
|
|
|
|
./usr/tests/lib/libutil/t_snprintb tests-lib-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/lib/semaphore tests-lib-tests
|
|
|
|
./usr/tests/lib/semaphore/pthread tests-lib-tests
|
|
|
|
./usr/tests/lib/semaphore/pthread/Atffile tests-lib-tests atf,rump
|
|
|
|
./usr/tests/lib/semaphore/pthread/Kyuafile tests-lib-tests atf,rump,kyua
|
|
|
|
./usr/tests/lib/semaphore/pthread/t_sem_pth tests-lib-tests atf,rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/libexec tests-lib-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/libexec/Atffile tests-lib-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/libexec/Kyuafile tests-lib-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/libexec/ld.elf_so tests-libexec-tests
|
|
|
|
./usr/tests/libexec/ld.elf_so/data tests-libexec-tests atf
|
|
|
|
./usr/tests/libexec/ld.elf_so/h_helper_symver_dso0 tests-libexec-tests atf
|
|
|
|
./usr/tests/libexec/ld.elf_so/h_helper_symver_dso1 tests-libexec-tests atf
|
|
|
|
./usr/tests/libexec/ld.elf_so/h_helper_symver_dso2 tests-libexec-tests atf
|
|
|
|
./usr/tests/modules tests-sys-tests
|
|
|
|
./usr/tests/net tests-net-tests
|
|
|
|
./usr/tests/net/bpf tests-net-tests
|
|
|
|
./usr/tests/net/bpf/Atffile tests-net-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/net/bpf/Kyuafile tests-net-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/net/bpf/t_bpf tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/bpf/t_div-by-zero tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/bpfilter tests-net-tests
|
|
|
|
./usr/tests/net/bpfilter/Atffile tests-net-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/net/bpfilter/Kyuafile tests-net-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/net/bpfilter/t_bpfilter tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/carp tests-net-tests
|
|
|
|
./usr/tests/net/carp/Atffile tests-net-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/net/carp/Kyuafile tests-net-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/net/carp/t_basic tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/fdpass tests-net-tests
|
|
|
|
./usr/tests/net/icmp tests-net-tests
|
|
|
|
./usr/tests/net/icmp/Atffile tests-net-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/net/icmp/Kyuafile tests-net-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/net/icmp/t_forward tests-net-tests atf,rump
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/net/icmp/t_forward tests-net-tests atf,rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/net/icmp/t_ping tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/icmp/t_ping2 tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/if tests-net-tests
|
|
|
|
./usr/tests/net/if/Atffile tests-net-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/net/if/Kyuafile tests-net-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/net/if/t_compat tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/if_loop tests-net-tests
|
|
|
|
./usr/tests/net/if_loop/Atffile tests-net-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/net/if_loop/Kyuafile tests-net-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/net/if_loop/t_pr tests-net-tests atf,rump
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/net/mpls tests-net-tests
|
|
|
|
./usr/tests/net/mpls/Atffile tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/mpls/Kyuafile tests-net-tests atf,rump,kyua
|
|
|
|
./usr/tests/net/mpls/t_ldp_regen tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/mpls/t_ldp_static tests-net-tests obsolete
|
|
|
|
./usr/tests/net/mpls/t_mpls_fw tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/mpls/t_rfc4182 tests-net-tests atf,rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/net/net tests-net-tests
|
|
|
|
./usr/tests/net/net/t_raw tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/npf tests-net-tests
|
|
|
|
./usr/tests/net/npf/Atffile tests-net-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/net/npf/Kyuafile tests-net-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/net/npf/npftest.conf tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/npf/t_npf tests-net-tests atf,rump
|
|
|
|
./usr/tests/net/route tests-net-tests
|
|
|
|
./usr/tests/net/sys tests-net-tests
|
|
|
|
./usr/tests/net/sys/t_connect tests-obsolete obsolete
|
|
|
|
./usr/tests/net/sys/t_listen tests-obsolete obsolete
|
|
|
|
./usr/tests/net/sys/t_socketpair tests-obsolete obsolete
|
|
|
|
./usr/tests/rump tests-rump-tests
|
|
|
|
./usr/tests/rump/Atffile tests-rump-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/rump/Kyuafile tests-rump-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/rump/modautoload tests-rump-tests
|
|
|
|
./usr/tests/rump/modautoload/Atffile tests-rump-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/rump/modautoload/Kyuafile tests-rump-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/rump/modautoload/t_modautoload tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern tests-rump-tests
|
|
|
|
./usr/tests/rump/rumpkern/Atffile tests-rump-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/rump/rumpkern/Kyuafile tests-rump-tests atf,rump,kyua
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/rump/rumpkern/h_client tests-rump-tests
|
|
|
|
./usr/tests/rump/rumpkern/h_client/h_forkcli tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern/h_client/h_reboot tests-obsolete obsolete
|
|
|
|
./usr/tests/rump/rumpkern/h_client/h_reconcli tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern/h_client/h_sigcli tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern/h_client/h_simplecli tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern/h_client/h_stresscli tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern/h_server tests-rump-tests
|
|
|
|
./usr/tests/rump/rumpkern/h_server/h_simpleserver tests-rump-tests atf,rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/rump/rumpkern/t_copy tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern/t_kern tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern/t_lwproc tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern/t_modcmd tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern/t_modlinkset tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern/t_signals tests-rump-tests atf,rump
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/rump/rumpkern/t_sp tests-rump-tests atf,rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/rump/rumpkern/t_threads tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern/t_tsleep tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpkern/t_vm tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpnet tests-rump-tests
|
|
|
|
./usr/tests/rump/rumpnet/Atffile tests-rump-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/rump/rumpnet/Kyuafile tests-rump-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/rump/rumpnet/t_shmif tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpvfs tests-rump-tests
|
|
|
|
./usr/tests/rump/rumpvfs/Atffile tests-rump-tests atf,rump
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/rump/rumpvfs/Kyuafile tests-rump-tests atf,rump,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/rump/rumpvfs/t_basic tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpvfs/t_etfs tests-rump-tests atf,rump
|
|
|
|
./usr/tests/rump/rumpvfs/t_p2kifs tests-rump-tests atf,rump
|
|
|
|
./usr/tests/sbin tests-sbin-tests
|
|
|
|
./usr/tests/sbin/Atffile tests-sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/sbin/Kyuafile tests-sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/sbin/fsck_ffs tests-sbin-tests
|
|
|
|
./usr/tests/sbin/fsck_ffs/Atffile tests-sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/sbin/fsck_ffs/Kyuafile tests-sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/sbin/fsck_ffs/t_check_quotas tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/fsck_ffs/t_enable_quotas tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/ifconfig tests-sbin-tests
|
|
|
|
./usr/tests/sbin/ifconfig/Atffile tests-sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/sbin/ifconfig/Kyuafile tests-sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/sbin/ifconfig/t_nonexistent tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/newfs tests-sbin-tests
|
|
|
|
./usr/tests/sbin/newfs/Atffile tests-sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/sbin/newfs/Kyuafile tests-sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/sbin/newfs/t_enable_quotas tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/newfs_msdos tests-sbin-tests
|
|
|
|
./usr/tests/sbin/newfs_msdos/Atffile tests-sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/sbin/newfs_msdos/Kyuafile tests-sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/sbin/newfs_msdos/t_create tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/resize_ffs tests-sbin-tests
|
|
|
|
./usr/tests/sbin/resize_ffs/Atffile tests-sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/sbin/resize_ffs/Kyuafile tests-sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/sbin/resize_ffs/t_grow tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/resize_ffs/t_grow_swapped tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/resize_ffs/t_resize_ffs tests-obsolete obsolete
|
|
|
|
./usr/tests/sbin/resize_ffs/t_shrink tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/resize_ffs/t_shrink_swapped tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/resize_ffs/testdata.md5 tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/resize_ffs/testdata.tar.gz.base64 tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/route tests-sbin-tests
|
|
|
|
./usr/tests/sbin/route/Atffile tests-sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/sbin/route/Kyuafile tests-sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/sbin/route/t_missing tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/sysctl tests-sbin-tests
|
|
|
|
./usr/tests/sbin/sysctl/Atffile tests-sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/sbin/sysctl/Kyuafile tests-sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/sbin/sysctl/t_perm tests-sbin-tests atf
|
|
|
|
./usr/tests/sbin/sysctl/t_sysctl tests-sbin-tests atf
|
|
|
|
./usr/tests/share tests-sys-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/share/Atffile tests-sys-tests atf
|
|
|
|
./usr/tests/share/Kyuafile tests-sys-tests atf,kyua
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/share/examples tests-asm-tests
|
|
|
|
./usr/tests/share/examples/Atffile tests-asm-tests atf,share
|
|
|
|
./usr/tests/share/examples/Kyuafile tests-asm-tests atf,share,kyua
|
|
|
|
./usr/tests/share/examples/lutok tests-lutok-tests
|
|
|
|
./usr/tests/share/examples/lutok/Atffile tests-lutok-tests atf,kyua,share
|
|
|
|
./usr/tests/share/examples/lutok/Kyuafile tests-lutok-tests atf,kyua,share,kyua
|
|
|
|
./usr/tests/share/examples/lutok/examples_test tests-lutok-tests atf,kyua,share
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/share/examples/t_asm tests-asm-tests atf,share
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/share/mk tests-mk-tests
|
|
|
|
./usr/tests/share/mk/Atffile tests-mk-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/share/mk/Kyuafile tests-mk-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/share/mk/t_lib tests-mk-tests atf
|
|
|
|
./usr/tests/share/mk/t_own tests-mk-tests atf
|
|
|
|
./usr/tests/share/mk/t_prog tests-mk-tests atf
|
|
|
|
./usr/tests/share/mk/t_test tests-mk-tests atf
|
|
|
|
./usr/tests/sys tests-sys-tests
|
|
|
|
./usr/tests/sys/Atffile tests-sys-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/sys/Kyuafile tests-sys-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/sys/rc tests-sys-tests
|
|
|
|
./usr/tests/sys/rc/Atffile tests-sys-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/sys/rc/Kyuafile tests-sys-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/sys/rc/h_args tests-sys-tests atf
|
|
|
|
./usr/tests/sys/rc/h_simple tests-sys-tests atf
|
|
|
|
./usr/tests/sys/rc/t_rc_d_cli tests-sys-tests atf
|
|
|
|
./usr/tests/syscall tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_access tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_chroot tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_cmsg tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_dup tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_fsync tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_getgroups tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_getlogin tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_getpid tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_getrusage tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_getsid tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_gettimeofday tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_issetugid tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_itimer tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_kill tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_link tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_mincore tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_mkfifo tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_mknod tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_mmap tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_mprotect tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_msync tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_nanosleep tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_poll tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_pollts tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_pselect tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_recvmmsg tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_revoke tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_setrlimit tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_setuid tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_stat tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_timer tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_truncate tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_umask tests-obsolete obsolete
|
|
|
|
./usr/tests/syscall/t_unlink tests-obsolete obsolete
|
|
|
|
./usr/tests/toolchain tests-obsolete obsolete
|
|
|
|
./usr/tests/toolchain/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/toolchain/cc tests-obsolete obsolete
|
|
|
|
./usr/tests/toolchain/cc/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/toolchain/cc/t_hello tests-obsolete obsolete
|
|
|
|
./usr/tests/usr.bin tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/awk tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/awk/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/awk/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/awk/d_assign_NF.awk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_assign_NF.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_assign_NF.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_big_regexp.awk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_big_regexp.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_big_regexp.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_end1.awk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_end1.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_end1.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_end2.awk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_end2.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_end2.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_period.awk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_period.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_period.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_string1.awk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_string1.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_tolower.awk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_tolower.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_tolower.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_toupper.awk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_toupper.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/awk/d_toupper.out tests-usr.bin-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/usr.bin/awk/t_awk tests-usr.bin-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/basename tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/basename/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/basename/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/basename/t_basename tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/bzip2 tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/bzip2/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/bzip2/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/bzip2/d_sample1.bz2 tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/bzip2/d_sample1.ref tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/bzip2/d_sample2.bz2 tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/bzip2/d_sample2.ref tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/bzip2/d_sample3.bz2 tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/bzip2/d_sample3.ref tests-usr.bin-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/usr.bin/bzip2/t_bzip2 tests-usr.bin-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/cc tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/cc/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/cc/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/cc/t_hello tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/cmp tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/cmp/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/cmp/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/cmp/t_cmp tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/config/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/config/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/config/Makefile.regress tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/d_deffs_redef tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/d_loop tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/d_loop2 tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/d_no_pseudo tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/d_postponed_orphan tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/d_pseudo_parent tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/d_shadow_instance tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/files tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/files.regress tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/std.regress tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/support tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/config/support/arch tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/config/support/arch/regress tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/config/support/arch/regress/conf tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/support/arch/regress/conf/Makefile.regress tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/support/arch/regress/conf/files.regress tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/support/arch/regress/conf/std.regress tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/config/support/conf tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/config/support/conf/files tests-usr.bin-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/usr.bin/config/t_config tests-usr.bin-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/cut tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/cut/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/cut/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/cut/d_basic.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/cut/d_cut.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/cut/d_dflag.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/cut/d_dsflag.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/cut/d_latin1.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/cut/d_sflag.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/cut/d_utf8.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/cut/t_cut tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/diff tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/diff/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/diff/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/diff/d_mallocv1.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/diff/d_mallocv2.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/diff/t_diff tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/dirname tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/dirname/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/dirname/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/dirname/t_dirname tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/find tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/find/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/find/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/find/t_find tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/grep/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/grep/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/grep/d_basic.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_begin_end_a.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_begin_end_b.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_binary.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_context2_a.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_context2_b.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_context2_c.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_context_a.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_context_a.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_context_b.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_context_b.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_context_c.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_context_d.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_egrep.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_file_exp.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_file_exp.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_ignore_case.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_input tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_invert.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_invert.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_recurse.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_recurse_symlink.err tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_recurse_symlink.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_whole_line.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_word_regexps.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/d_zgrep.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/grep/t_grep tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/gzip tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/gzip/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/gzip/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/gzip/t_gzip tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/id tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/id/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/id/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/id/h_id tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/id/t_groups tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/id/t_id tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/id/t_whoami tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/infocmp tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/infocmp/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/infocmp/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/infocmp/t_terminfo tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/jot tests-usr.bin-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/usr.bin/jot/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/jot/Kyuafile tests-usr.bin-tests atf,kyua
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/usr.bin/jot/d_basic.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/jot/t_jot tests-usr.bin-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/m4 tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/m4/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/m4/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/m4/d_ff_after_dnl.m4.uue tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/m4/d_ff_after_dnl.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/m4/d_m4wrap-P.m4 tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/m4/d_m4wrap-P.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/m4/d_m4wrap.m4 tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/m4/d_m4wrap.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/m4/t_m4 tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/make/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/make/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/make/d_comment.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_comment.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_cond1.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_cond1.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_dotwait.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_dotwait.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_export.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_export.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_export_all.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_export_all.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_moderrs.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_moderrs.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_modmatch.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_modmatch.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_modmisc.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_modmisc.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_modorder.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_modorder.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_modts.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_modts.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_modword.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_modword.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_posix.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_posix.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_qequals.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_qequals.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_ternary.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_ternary.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_unmatchedvarparen.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_unmatchedvarparen.out tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/make/d_varcmd.mk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/d_varcmd.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/make/t_make tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/mkdep tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/mkdep/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/mkdep/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/mkdep/t_mkdep tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/nbperf tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/nbperf/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/nbperf/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/nbperf/h_nbperf tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/nbperf/hash_driver.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/nbperf/t_nbperf tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/netpgpverify tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/netpgpverify/Atffile tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/netpgpverify/Kyuafile tests-usr.bin-tests atf,kyua
|
|
|
|
./usr/tests/usr.bin/netpgpverify/t_netpgpverify tests-usr.bin-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/pr tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/pr/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/pr/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/pr/d_basic.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/pr/d_basic.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/pr/t_basic tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/rump_server tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/rump_server/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/rump_server/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/rump_server/t_disk tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/sdiff/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/sdiff/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/sdiff/d_dot.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_flags_l.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_flags_s.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_flags_w.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_iflags_a1.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_iflags_a2.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_iflags_b1.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_iflags_b2.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_iflags_c1.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_iflags_c2.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_iflags_d1.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_iflags_d2.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_input1 tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_input2 tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_oneline.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_oneline_a.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_oneline_b.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_same.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_short.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_tabends.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_tabends_a.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_tabends_b.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_tabends_c.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_tabs.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_tabs1.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/d_tabs2.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sdiff/t_sdiff tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sed tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/sed/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/sed/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/sed/d_c2048.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sed/t_sed tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/shmif_dumpbus tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/shmif_dumpbus/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/shmif_dumpbus/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/shmif_dumpbus/d_pcap.out.bz2.uue tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/shmif_dumpbus/d_pkthdrs.out.bz2.uue tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/shmif_dumpbus/shmbus.bz2.uue tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/shmif_dumpbus/t_basic tests-usr.bin-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/sort tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/sort/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/sort/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/sort/d_any_char_dflag_out.txt tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sort/d_any_char_fflag_out.txt tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sort/d_any_char_iflag_out.txt tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sort/d_any_char_in.txt tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/sort/t_sort tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/tmux tests-usr.bin-tests
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/tmux/Atffile tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/tmux/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/tmux/t_tmux tests-usr.bin-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/usr.bin/tr tests-usr.bin-tests
|
|
|
|
./usr/tests/usr.bin/tr/Atffile tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/tr/Kyuafile tests-usr.bin-tests atf,kyua
|
|
|
|
./usr/tests/usr.bin/tr/t_basic tests-usr.bin-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/unifdef tests-usr.bin-tests
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/unifdef/Atffile tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/unifdef/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/unifdef/d_basic.in tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/unifdef/d_basic.out tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/unifdef/t_basic tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint tests-usr.bin-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/usr.bin/xlint/Atffile tests-usr.bin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.bin/xlint/Kyuafile tests-usr.bin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.bin/xlint/lint1 tests-usr.bin-tests
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/usr.bin/xlint/lint1/Atffile tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/Kyuafile tests-usr.bin-tests atf,kyua
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_alignof.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_c99_complex_num.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_c99_decls_after_stmt.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_c99_decls_after_stmt2.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_c99_for_loops.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_c99_func.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_c99_recursive_init.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_c99_struct_init.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_c99_union_init1.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_c99_union_init2.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_c99_union_init3.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_c9x_array_init.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_c9x_recursive_init.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_cast_init.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_cast_init2.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_cast_lhs.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_compound_literals1.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_compound_literals2.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_constant_conv1.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_constant_conv2.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_cvt_in_ternary.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_ellipsis_in_switch.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_gcc_compound_statements1.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_gcc_compound_statements2.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_gcc_compound_statements3.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_gcc_func.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_gcc_variable_array_init.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_incorrect_array_size.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_long_double_int.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_nested_structs.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_nolimit_init.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_packed_structs.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_shift_to_narrower_type.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_type_conv1.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_type_conv2.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_type_conv3.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_typename_as_var.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/d_zero_sized_arrays.c tests-usr.bin-tests atf
|
|
|
|
./usr/tests/usr.bin/xlint/lint1/t_integration tests-usr.bin-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.sbin tests-usr.sbin-tests
|
|
|
|
./usr/tests/usr.sbin/Atffile tests-usr.sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.sbin/Kyuafile tests-usr.sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.sbin/mtree tests-usr.sbin-tests
|
|
|
|
./usr/tests/usr.sbin/mtree/Atffile tests-usr.sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.sbin/mtree/Kyuafile tests-usr.sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.sbin/mtree/d_convert.in tests-usr.sbin-tests atf
|
|
|
|
./usr/tests/usr.sbin/mtree/d_convert_C.out tests-usr.sbin-tests atf
|
|
|
|
./usr/tests/usr.sbin/mtree/d_convert_C_S.out tests-usr.sbin-tests atf
|
|
|
|
./usr/tests/usr.sbin/mtree/d_convert_D.out tests-usr.sbin-tests atf
|
|
|
|
./usr/tests/usr.sbin/mtree/d_convert_D_S.out tests-usr.sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.sbin/mtree/d_create.out tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.sbin/mtree/d_merge.in tests-usr.sbin-tests atf
|
|
|
|
./usr/tests/usr.sbin/mtree/d_merge_C_M.out tests-usr.sbin-tests atf
|
|
|
|
./usr/tests/usr.sbin/mtree/d_merge_C_M_S.out tests-usr.sbin-tests atf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/usr.sbin/mtree/mtree_d_create.out tests-usr.sbin-tests atf
|
|
|
|
./usr/tests/usr.sbin/mtree/netbsd6_d_create.out tests-usr.sbin-tests atf
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.sbin/mtree/t_mtree tests-usr.sbin-tests atf
|
|
|
|
./usr/tests/usr.sbin/tcpdump tests-usr.sbin-tests
|
|
|
|
./usr/tests/usr.sbin/tcpdump/Atffile tests-usr.sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.sbin/tcpdump/Kyuafile tests-usr.sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.sbin/tcpdump/t_tcpdump tests-usr.sbin-tests atf
|
|
|
|
./usr/tests/usr.sbin/traceroute tests-usr.sbin-tests
|
|
|
|
./usr/tests/usr.sbin/traceroute/Atffile tests-usr.sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.sbin/traceroute/Kyuafile tests-usr.sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.sbin/traceroute/t_traceroute tests-usr.sbin-tests atf
|
|
|
|
./usr/tests/usr.sbin/useradd tests-usr.sbin-tests
|
|
|
|
./usr/tests/usr.sbin/useradd/Atffile tests-usr.sbin-tests atf
|
2013-02-26 09:24:42 +01:00
|
|
|
./usr/tests/usr.sbin/useradd/Kyuafile tests-usr.sbin-tests atf,kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/usr.sbin/useradd/t_useradd tests-usr.sbin-tests atf
|
|
|
|
./usr/tests/util tests-obsolete obsolete
|
|
|
|
./usr/tests/util/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_assign_NF.awk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_assign_NF.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_assign_NF.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_big_regexp.awk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_big_regexp.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_big_regexp.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_end1.awk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_end1.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_end1.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_end2.awk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_end2.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_end2.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_period.awk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_period.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_period.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_string1.awk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_string1.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_tolower.awk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_tolower.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_tolower.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_toupper.awk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_toupper.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/d_toupper.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/awk/t_awk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/bzip2 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/bzip2/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/bzip2/d_sample1.bz2 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/bzip2/d_sample1.ref tests-obsolete obsolete
|
|
|
|
./usr/tests/util/bzip2/d_sample2.bz2 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/bzip2/d_sample2.ref tests-obsolete obsolete
|
|
|
|
./usr/tests/util/bzip2/d_sample3.bz2 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/bzip2/d_sample3.ref tests-obsolete obsolete
|
|
|
|
./usr/tests/util/bzip2/t_bzip2 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/Makefile.regress tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/d_deffs_redef tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/d_loop tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/d_loop2 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/d_no_pseudo tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/d_postponed_orphan tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/d_pseudo_parent tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/d_shadow_instance tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/files tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/files.regress tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/std.regress tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/support tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/support/arch tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/support/arch/regress tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/support/arch/regress/conf tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/support/arch/regress/conf/Makefile.regress tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/support/arch/regress/conf/files.regress tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/support/arch/regress/conf/std.regress tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/support/conf tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/support/conf/files tests-obsolete obsolete
|
|
|
|
./usr/tests/util/config/t_config tests-obsolete obsolete
|
|
|
|
./usr/tests/util/cut tests-obsolete obsolete
|
|
|
|
./usr/tests/util/cut/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/cut/d_basic.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/cut/d_cut.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/cut/d_dflag.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/cut/d_dsflag.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/cut/d_latin1.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/cut/d_sflag.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/cut/d_utf8.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/cut/t_cut tests-obsolete obsolete
|
|
|
|
./usr/tests/util/df tests-obsolete obsolete
|
|
|
|
./usr/tests/util/df/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/df/h_df tests-obsolete obsolete
|
|
|
|
./usr/tests/util/df/t_df tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_basic.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_begin_end_a.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_begin_end_b.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_binary.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_context2_a.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_context2_b.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_context2_c.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_context_a.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_context_a.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_context_b.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_context_b.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_context_c.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_context_d.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_egrep.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_file_exp.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_file_exp.inout tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/util/grep/d_file_exp.out tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/util/grep/d_ignore_case.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_input tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_invert.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_invert.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_recurse.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_recurse_symlink.err tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_recurse_symlink.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_whole_line.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_word_regexps.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/d_zgrep.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/grep/t_grep tests-obsolete obsolete
|
|
|
|
./usr/tests/util/id tests-obsolete obsolete
|
|
|
|
./usr/tests/util/id/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/id/h_id tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/util/id/libfake_pic.a tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/util/id/t_groups tests-obsolete obsolete
|
|
|
|
./usr/tests/util/id/t_id tests-obsolete obsolete
|
|
|
|
./usr/tests/util/id/t_whoami tests-obsolete obsolete
|
|
|
|
./usr/tests/util/m4 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/m4/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/m4/d_ff_after_dnl.m4.uue tests-obsolete obsolete
|
|
|
|
./usr/tests/util/m4/d_ff_after_dnl.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/m4/d_m4wrap-P.m4 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/m4/d_m4wrap-P.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/m4/d_m4wrap.m4 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/m4/d_m4wrap.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/m4/t_m4 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_comment.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_comment.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_cond1.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_cond1.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_dotwait.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_dotwait.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_export.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_export.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_export_all.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_export_all.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_moderrs.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_moderrs.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_modmatch.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_modmatch.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_modmisc.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_modmisc.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_modorder.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_modorder.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_modts.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_modts.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_modword.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_modword.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_posix.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_posix.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_qequals.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_qequals.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_ternary.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_ternary.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_unmatchedvarparen.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_unmatchedvarparen.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_varcmd.mk tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/d_varcmd.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/make/t_make tests-obsolete obsolete
|
|
|
|
./usr/tests/util/mtree tests-obsolete obsolete
|
|
|
|
./usr/tests/util/mtree/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/mtree/d_convert.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/mtree/d_convert_C.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/mtree/d_convert_C_S.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/mtree/d_convert_D.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/mtree/d_convert_D_S.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/mtree/d_create.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/mtree/d_merge.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/mtree/d_merge_C_M.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/mtree/d_merge_C_M_S.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/mtree/t_mtree tests-obsolete obsolete
|
|
|
|
./usr/tests/util/ps tests-obsolete obsolete
|
|
|
|
./usr/tests/util/ps/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/ps/keywords tests-obsolete obsolete
|
|
|
|
./usr/tests/util/ps/t_ps tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_dot.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_flags_l.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_flags_s.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_flags_w.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_iflags_a1.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_iflags_a2.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_iflags_b1.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_iflags_b2.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_iflags_c1.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_iflags_c2.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_iflags_d1.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_iflags_d2.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_input1 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_input2 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_oneline.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_oneline_a.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_oneline_b.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_same.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_short.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_tabends.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_tabends_a.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_tabends_b.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_tabends_c.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_tabs.out tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_tabs1.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/d_tabs2.in tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sdiff/t_sdiff tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sh tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sh/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sh/t_compexit tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/util/sh/t_evaltested tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/util/sh/t_exit tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sh/t_exitstatus tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sh/t_expand tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sh/t_fsplit tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sh/t_here tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sh/t_set_e tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sh/t_varquote tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sh/t_wait tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sort tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sort/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sort/d_any_char_dflag_out.txt tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sort/d_any_char_fflag_out.txt tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sort/d_any_char_iflag_out.txt tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sort/d_any_char_in.txt tests-obsolete obsolete
|
|
|
|
./usr/tests/util/sort/t_sort tests-obsolete obsolete
|
|
|
|
./usr/tests/util/systrace tests-obsolete obsolete
|
|
|
|
./usr/tests/util/systrace/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/systrace/h_have_systrace tests-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/tests/util/systrace/id.policy tests-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/tests/util/systrace/t_id tests-obsolete obsolete
|
|
|
|
./usr/tests/util/t_basename tests-obsolete obsolete
|
|
|
|
./usr/tests/util/t_cp tests-obsolete obsolete
|
|
|
|
./usr/tests/util/t_dd tests-obsolete obsolete
|
|
|
|
./usr/tests/util/t_dirname tests-obsolete obsolete
|
|
|
|
./usr/tests/util/t_expr tests-obsolete obsolete
|
|
|
|
./usr/tests/util/t_gzip tests-obsolete obsolete
|
|
|
|
./usr/tests/util/t_pax tests-obsolete obsolete
|
|
|
|
./usr/tests/util/t_sort tests-obsolete obsolete
|
|
|
|
./usr/tests/util/t_tar tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1 tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/Atffile tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_alignof.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_c99_complex_num.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_c99_decls_after_stmt.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_c99_decls_after_stmt2.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_c99_for_loops.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_c99_func.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_c99_recursive_init.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_c99_struct_init.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_c99_union_init1.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_c99_union_init2.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_c99_union_init3.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_c9x_array_init.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_c9x_recursive_init.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_cast_init.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_cast_init2.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_cast_lhs.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_compound_literals1.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_compound_literals2.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_constant_conv1.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_constant_conv2.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_cvt_in_ternary.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_ellipsis_in_switch.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_gcc_compound_statements1.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_gcc_compound_statements2.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_gcc_compound_statements3.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_gcc_func.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_gcc_variable_array_init.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_incorrect_array_size.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_long_double_int.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_nested_structs.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_nolimit_init.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_packed_structs.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_shift_to_narrower_type.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_type_conv1.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_type_conv2.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_type_conv3.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_typename_as_var.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/d_zero_sized_arrays.c tests-obsolete obsolete
|
|
|
|
./usr/tests/util/xlint/lint1/t_integration tests-obsolete obsolete
|