adapt to ${CC_WNO_MAYBE_UNINITIALIZED}

Use ${CC_WNO_MAYBE_UNINITIALIZED} instead of
the older style more complex expressions.

Remove workarounds if they were for a specific
version of gcc < 10.

convert HAVE_GCC == 7 to HAVE_GCC >= 7.

with GCC 7, apply -Wno-error=maybe-uninitialized to parser.cpp.

i don't really understand how to remove this warning, someone else
could though, so feel free to :-)

In file included from /usr/src/external/bsd/atf/dist/tools/parser.cpp:33:0:
/usr/src/external/bsd/atf/dist/tools/parser.hpp: In member function 'tools::parser::token tools::parser::tokenizer<IS>::next() [with IS = std::basic_istream<char>]':
/usr/src/external/bsd/atf/dist/tools/parser.hpp:98:8: warning: '<anonymous>.tools::parser::token::m_line' may be used uninitialized in this function [-Wmaybe-uninitialized]
struct token {
^~~~~

branches: 1.5.4; 1.5.8; 1.5.30;
Homogenize reachover build file structure with that of kyua-cli:

- Move the majority of the common build definitions to the top-level
Makefile.inc and ensure this gets included everywhere.
- Move the bconfig.h file to the top-level directory.
- Add a statically-generated defs.h file instead of creating one
during the build. Easier to understand and less chances for things
to go wrong.
- Make sure all files using ATF_VERSION have the right dependency to
trigger a rebuild when the value changes.
- Clean up stale -I flags.

This is all mostly for simplicity reasons and to reduce the cognitive
load required to understand the build of the atf and kyua-* packages.

I have tested this with both MKKYUA=no/yes and non-clean/clean builds
so hopefully I got the details right. But if not, let me know please.

Stop using bconfig.h in the tools code.

Just assume the code is being built for NetBSD for simplicity reasons.

Remove defs.hpp.

Because we now own the 'tools' subdirectory in the tree, we can yank some
of the upstream autoconf-related complexity. Start doing so by removing
defs.hpp and using the real compiler attributes where necessary.

Update reachover build files for atf-0.20.

Adjust reachover Makefiles for atf-0.19.

The main change here is that the atf-config, atf-report, atf-run and
atf-version tools no longer depend on libatf-c nor libatf-c++. Instead,
they depend on an internal libtools.a that contains code specifically
for these tools and nothing else, making them self-contained.

convert HAVE_GCC == 7 to HAVE_GCC >= 7.

with GCC 7, apply -Wno-error=maybe-uninitialized to parser.cpp.

i don't really understand how to remove this warning, someone else
could though, so feel free to :-)

In file included from /usr/src/external/bsd/atf/dist/tools/parser.cpp:33:0:
/usr/src/external/bsd/atf/dist/tools/parser.hpp: In member function 'tools::parser::token tools::parser::tokenizer<IS>::next() [with IS = std::basic_istream<char>]':
/usr/src/external/bsd/atf/dist/tools/parser.hpp:98:8: warning: '<anonymous>.tools::parser::token::m_line' may be used uninitialized in this function [-Wmaybe-uninitialized]
struct token {
^~~~~

branches: 1.5.4; 1.5.8; 1.5.30;
Homogenize reachover build file structure with that of kyua-cli:

- Move the majority of the common build definitions to the top-level
Makefile.inc and ensure this gets included everywhere.
- Move the bconfig.h file to the top-level directory.
- Add a statically-generated defs.h file instead of creating one
during the build. Easier to understand and less chances for things
to go wrong.
- Make sure all files using ATF_VERSION have the right dependency to
trigger a rebuild when the value changes.
- Clean up stale -I flags.

This is all mostly for simplicity reasons and to reduce the cognitive
load required to understand the build of the atf and kyua-* packages.

I have tested this with both MKKYUA=no/yes and non-clean/clean builds
so hopefully I got the details right. But if not, let me know please.

Stop using bconfig.h in the tools code.

Just assume the code is being built for NetBSD for simplicity reasons.

Remove defs.hpp.

Because we now own the 'tools' subdirectory in the tree, we can yank some
of the upstream autoconf-related complexity. Start doing so by removing
defs.hpp and using the real compiler attributes where necessary.

Update reachover build files for atf-0.20.

Adjust reachover Makefiles for atf-0.19.

The main change here is that the atf-config, atf-report, atf-run and
atf-version tools no longer depend on libatf-c nor libatf-c++. Instead,
they depend on an internal libtools.a that contains code specifically
for these tools and nothing else, making them self-contained.

with GCC 7, apply -Wno-error=maybe-uninitialized to parser.cpp.

i don't really understand how to remove this warning, someone else
could though, so feel free to :-)

In file included from /usr/src/external/bsd/atf/dist/tools/parser.cpp:33:0:
/usr/src/external/bsd/atf/dist/tools/parser.hpp: In member function 'tools::parser::token tools::parser::tokenizer<IS>::next() [with IS = std::basic_istream<char>]':
/usr/src/external/bsd/atf/dist/tools/parser.hpp:98:8: warning: '<anonymous>.tools::parser::token::m_line' may be used uninitialized in this function [-Wmaybe-uninitialized]
struct token {
^~~~~

branches: 1.5.4; 1.5.8;
Homogenize reachover build file structure with that of kyua-cli:

- Move the majority of the common build definitions to the top-level
Makefile.inc and ensure this gets included everywhere.
- Move the bconfig.h file to the top-level directory.
- Add a statically-generated defs.h file instead of creating one
during the build. Easier to understand and less chances for things
to go wrong.
- Make sure all files using ATF_VERSION have the right dependency to
trigger a rebuild when the value changes.
- Clean up stale -I flags.

This is all mostly for simplicity reasons and to reduce the cognitive
load required to understand the build of the atf and kyua-* packages.

I have tested this with both MKKYUA=no/yes and non-clean/clean builds
so hopefully I got the details right. But if not, let me know please.

Stop using bconfig.h in the tools code.

Just assume the code is being built for NetBSD for simplicity reasons.

Remove defs.hpp.

Because we now own the 'tools' subdirectory in the tree, we can yank some
of the upstream autoconf-related complexity. Start doing so by removing
defs.hpp and using the real compiler attributes where necessary.

Update reachover build files for atf-0.20.

Adjust reachover Makefiles for atf-0.19.

The main change here is that the atf-config, atf-report, atf-run and
atf-version tools no longer depend on libatf-c nor libatf-c++. Instead,
they depend on an internal libtools.a that contains code specifically
for these tools and nothing else, making them self-contained.

branches: 1.5.4; 1.5.8;
Homogenize reachover build file structure with that of kyua-cli:

- Move the majority of the common build definitions to the top-level
Makefile.inc and ensure this gets included everywhere.
- Move the bconfig.h file to the top-level directory.
- Add a statically-generated defs.h file instead of creating one
during the build. Easier to understand and less chances for things
to go wrong.
- Make sure all files using ATF_VERSION have the right dependency to
trigger a rebuild when the value changes.
- Clean up stale -I flags.

This is all mostly for simplicity reasons and to reduce the cognitive
load required to understand the build of the atf and kyua-* packages.

I have tested this with both MKKYUA=no/yes and non-clean/clean builds
so hopefully I got the details right. But if not, let me know please.

Stop using bconfig.h in the tools code.

Just assume the code is being built for NetBSD for simplicity reasons.

Remove defs.hpp.

Because we now own the 'tools' subdirectory in the tree, we can yank some
of the upstream autoconf-related complexity. Start doing so by removing
defs.hpp and using the real compiler attributes where necessary.

Update reachover build files for atf-0.20.

Adjust reachover Makefiles for atf-0.19.

The main change here is that the atf-config, atf-report, atf-run and
atf-version tools no longer depend on libatf-c nor libatf-c++. Instead,
they depend on an internal libtools.a that contains code specifically
for these tools and nothing else, making them self-contained.

Rebase to HEAD as of a few days ago.

file Makefile was added on branch tls-maxphys on 2014-08-19 23:45:55 +0000

sync with head.

for a reference, the tree before this commit was tagged
as yamt-pagecache-tag8.

this commit was splitted into small chunks to avoid
a limitation of cvs. ("Protocol error: too many arguments")

file Makefile was added on branch yamt-pagecache on 2014-05-22 15:40:13 +0000