d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
freebsd-skq/usr.bin/getconf/Makefile

45 lines
1.1 KiB
Makefile
Raw Permalink Normal View History

Make this work under non-C locales. PR: misc/45460 Approved by: re
2002-11-25 09:00:05 +00:00
# $FreeBSD$
Hello, getconf. This is a slight reinvention of the wheel^H^H^H^H^HPOSIX.2 and X/Open utility, and rather more complicated than necessary.
2000-04-26 02:36:54 +00:00
usr.bin/getconf: add some initial tests Items tested via this commit are: - Some basic POSIX constants. - Some valid programming environments with -v. - Some invalid programming environments via -v. NOTE: this test makes assumptions about ILP32/LP32 vs LP64 that are currently not true on all architectures to avoid hardcoding some architectures in the tests. I'm working on improving getconf(1) to be more sane about handling ILP32/LP32 vs LP64. Future commits are coming soon to address this. MFC after: 2 weeks Tested with: amd64, i386 Sponsored by: Dell EMC Isilon
2017-05-18 01:43:30 +00:00
.include <src.opts.mk>
Hello, getconf. This is a slight reinvention of the wheel^H^H^H^H^HPOSIX.2 and X/Open utility, and rather more complicated than necessary.
2000-04-26 02:36:54 +00:00
PROG= getconf
Move unsigned limits to a separate table/recognizer and display them using the appropriate (unsigned) format specification. This prevents integer overflow when ULLONG_MAX and (on some architectures) ULONG_MAX are used to initialize an intmax_t and then displayed as the signed value -1. (A different approach was suggested in the bug report, which I did not use.) If other limits are defined to be unsigned, they could be moved here. PR: 164049 Reported by: Marcus Reid
2018-05-23 02:51:56 +00:00
SRCS= confstr.c getconf.c limits.c pathconf.c progenv.c sysconf.c \
unsigned_limits.c
Unbreak for the case where ``make obj'' was run first.
2000-04-26 07:00:46 +00:00
CFLAGS+= -I${.CURDIR}
Completely revamp the way getconf(1) works, for better adherence to the intent of the Standard. - Make getconf able to distinguish between configuration variables which are entirely unknown and those which are merely not defined in the compilation environment. The latter now get a more appropriate "undefined\n" result rather than a diagnostic. This may not be exactly right, but it's closer to the intent of the Standard than the previous behavior. - Support ``programming environments'' by validating that the environment requested with the `-v' flag is the one-and-only execution environment. (If more environments are supported for some platforms in the future, multiple getconf(1) executables will be required, but a simple edit in progenv.gperf will enable automatic support for it.) Document POSIX standard programming environments. - Add all of the 1003.1-2001 configuration variables. FreeBSD does not support all of these (including some that are mandatory); getconf will later be fixed to break the world should a required variable not be defined. As a result of all these changes, gperf is no longer adequate. Keep the overall format and names of the files for now, to preserve revision history. Use an awk script to process the .gperf files into C source, which does a few things that gperf, as a more general tool, cannot do. The keyword recognition function is no longer a perfect hash function. This may obviate the need for gperf in the source tree. - Add a small compile-time regression test to break the build if any of the .gperf files declare conflicting token sets. (gperf itself would have done this for the simple case of duplicate tokens in the same input file.)
2002-09-19 03:39:03 +00:00
CLEANFILES+= confstr.c limits.c pathconf.c progenv.c sysconf.c \
confstr.names limits.names pathconf.names sysconf.names \
Move unsigned limits to a separate table/recognizer and display them using the appropriate (unsigned) format specification. This prevents integer overflow when ULLONG_MAX and (on some architectures) ULONG_MAX are used to initialize an intmax_t and then displayed as the signed value -1. (A different approach was suggested in the bug report, which I did not use.) If other limits are defined to be unsigned, they could be moved here. PR: 164049 Reported by: Marcus Reid
2018-05-23 02:51:56 +00:00
conflicting.names unique.names unsigned_limits.names
Hello, getconf. This is a slight reinvention of the wheel^H^H^H^H^HPOSIX.2 and X/Open utility, and rather more complicated than necessary.
2000-04-26 02:36:54 +00:00
Completely revamp the way getconf(1) works, for better adherence to the intent of the Standard. - Make getconf able to distinguish between configuration variables which are entirely unknown and those which are merely not defined in the compilation environment. The latter now get a more appropriate "undefined\n" result rather than a diagnostic. This may not be exactly right, but it's closer to the intent of the Standard than the previous behavior. - Support ``programming environments'' by validating that the environment requested with the `-v' flag is the one-and-only execution environment. (If more environments are supported for some platforms in the future, multiple getconf(1) executables will be required, but a simple edit in progenv.gperf will enable automatic support for it.) Document POSIX standard programming environments. - Add all of the 1003.1-2001 configuration variables. FreeBSD does not support all of these (including some that are mandatory); getconf will later be fixed to break the world should a required variable not be defined. As a result of all these changes, gperf is no longer adequate. Keep the overall format and names of the files for now, to preserve revision history. Use an awk script to process the .gperf files into C source, which does a few things that gperf, as a more general tool, cannot do. The keyword recognition function is no longer a perfect hash function. This may obviate the need for gperf in the source tree. - Add a small compile-time regression test to break the build if any of the .gperf files declare conflicting token sets. (gperf itself would have done this for the simple case of duplicate tokens in the same input file.)
2002-09-19 03:39:03 +00:00
.SUFFIXES: .gperf .names
.PHONY: conflicts
all: conflicts
Hello, getconf. This is a slight reinvention of the wheel^H^H^H^H^HPOSIX.2 and X/Open utility, and rather more complicated than necessary.
2000-04-26 02:36:54 +00:00
Make the `.gperf.c` suffix rule depend on fake-gperf.awk Parameterize out fake-gperf.awk to avoid duplicating the path MFC after: 2 weeks Sponsored by: Dell EMC Isilon
2017-05-18 01:35:07 +00:00
FAKE_GPERF= ${.CURDIR}/fake-gperf.awk
.gperf.c: ${FAKE_GPERF}
LC_ALL=C awk -f ${FAKE_GPERF} ${.IMPSRC} >${.TARGET}
Completely revamp the way getconf(1) works, for better adherence to the intent of the Standard. - Make getconf able to distinguish between configuration variables which are entirely unknown and those which are merely not defined in the compilation environment. The latter now get a more appropriate "undefined\n" result rather than a diagnostic. This may not be exactly right, but it's closer to the intent of the Standard than the previous behavior. - Support ``programming environments'' by validating that the environment requested with the `-v' flag is the one-and-only execution environment. (If more environments are supported for some platforms in the future, multiple getconf(1) executables will be required, but a simple edit in progenv.gperf will enable automatic support for it.) Document POSIX standard programming environments. - Add all of the 1003.1-2001 configuration variables. FreeBSD does not support all of these (including some that are mandatory); getconf will later be fixed to break the world should a required variable not be defined. As a result of all these changes, gperf is no longer adequate. Keep the overall format and names of the files for now, to preserve revision history. Use an awk script to process the .gperf files into C source, which does a few things that gperf, as a more general tool, cannot do. The keyword recognition function is no longer a perfect hash function. This may obviate the need for gperf in the source tree. - Add a small compile-time regression test to break the build if any of the .gperf files declare conflicting token sets. (gperf itself would have done this for the simple case of duplicate tokens in the same input file.)
2002-09-19 03:39:03 +00:00
.gperf.names:
Make this work under non-C locales. PR: misc/45460 Approved by: re
2002-11-25 09:00:05 +00:00
LC_ALL=C awk '/^[_A-Z]/ { print; }' ${.IMPSRC} | \
sed -e 's/,$$//' >${.TARGET}
Completely revamp the way getconf(1) works, for better adherence to the intent of the Standard. - Make getconf able to distinguish between configuration variables which are entirely unknown and those which are merely not defined in the compilation environment. The latter now get a more appropriate "undefined\n" result rather than a diagnostic. This may not be exactly right, but it's closer to the intent of the Standard than the previous behavior. - Support ``programming environments'' by validating that the environment requested with the `-v' flag is the one-and-only execution environment. (If more environments are supported for some platforms in the future, multiple getconf(1) executables will be required, but a simple edit in progenv.gperf will enable automatic support for it.) Document POSIX standard programming environments. - Add all of the 1003.1-2001 configuration variables. FreeBSD does not support all of these (including some that are mandatory); getconf will later be fixed to break the world should a required variable not be defined. As a result of all these changes, gperf is no longer adequate. Keep the overall format and names of the files for now, to preserve revision history. Use an awk script to process the .gperf files into C source, which does a few things that gperf, as a more general tool, cannot do. The keyword recognition function is no longer a perfect hash function. This may obviate the need for gperf in the source tree. - Add a small compile-time regression test to break the build if any of the .gperf files declare conflicting token sets. (gperf itself would have done this for the simple case of duplicate tokens in the same input file.)
2002-09-19 03:39:03 +00:00
conflicts: conflicting.names unique.names
@if test `wc -l <conflicting.names` != `wc -l <unique.names`; then \
echo "Name conflicts found!" >&2; \
exit 1; \
fi
# pathconf.names is not included here because pathconf names are
# syntactically distinct from the other kinds.
conflicting.names: confstr.names limits.names sysconf.names
cat ${.ALLSRC} >${.TARGET}
unique.names: conflicting.names
Make this work under non-C locales. PR: misc/45460 Approved by: re
2002-11-25 09:00:05 +00:00
LC_ALL=C sort -u ${.ALLSRC} >${.TARGET}
Hello, getconf. This is a slight reinvention of the wheel^H^H^H^H^HPOSIX.2 and X/Open utility, and rather more complicated than necessary.
2000-04-26 02:36:54 +00:00
Add HAS_TESTS to all Makefiles that are currently using the `SUBDIR.${MK_TESTS}+= tests` idiom. This is a follow up to r321912.
2017-08-02 08:50:42 +00:00
HAS_TESTS=
MFhead@r321912
2017-08-02 08:38:36 +00:00
SUBDIR.${MK_TESTS}+= tests
usr.bin/getconf: add some initial tests Items tested via this commit are: - Some basic POSIX constants. - Some valid programming environments with -v. - Some invalid programming environments via -v. NOTE: this test makes assumptions about ILP32/LP32 vs LP64 that are currently not true on all architectures to avoid hardcoding some architectures in the tests. I'm working on improving getconf(1) to be more sane about handling ILP32/LP32 vs LP64. Future commits are coming soon to address this. MFC after: 2 weeks Tested with: amd64, i386 Sponsored by: Dell EMC Isilon
2017-05-18 01:43:30 +00:00
Hello, getconf. This is a slight reinvention of the wheel^H^H^H^H^HPOSIX.2 and X/Open utility, and rather more complicated than necessary.
2000-04-26 02:36:54 +00:00
.include <bsd.prog.mk>
Reference in New Issue Copy Permalink