blob: 7feefa49a718c276101f65d2d045e3f174e07f38 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
?RCS: $Id$
?RCS:
?RCS: Copyright (c) 1991-1997, 2004-2006, Raphael Manfredi
?RCS:
?RCS: You may redistribute only under the terms of the Artistic Licence,
?RCS: as specified in the README file that comes with the distribution.
?RCS: You may reuse parts of this distribution only within the terms of
?RCS: that same Artistic Licence; a copy of which may be found at the root
?RCS: of the source tree for dist 4.0.
?RCS:
?RCS: $Log: keyword.U,v $
?RCS: Revision 3.0 1993/08/18 12:10:08 ram
?RCS: Baseline for dist 3.0 netwide release.
?RCS:
?MAKE:d_const: cat cc ccflags Setvar
?MAKE: -pick add $@ %<
?S:d_<KEY>:
?S: This variable conditionally defines the HASCONST symbol, which
?S: indicates to the C program that this C compiler knows about the
?S: <KEY> type.
?S:.
?C:HAS<%KEY> ~ %<:
?C: This symbol, if defined, indicates that this C compiler knows about
?C: the <KEY> type. There is no need to actually test for that symbol
?C: within your programs. The mere use of the "<KEY>" keyword will
?C: trigger the necessary tests.
?C:.
?H:?%<:#$d_<KEY> HAS<%KEY> /**/
?H:?%<:#ifndef HAS<%KEY>
?H:?%<:#define <KEY>
?H:?%<:#endif
?H:.
?W:%<:<KEY>
?LINT:set d_<KEY>
?LINT:known <KEY>
: check for <KEY> keyword
echo " "
echo 'Checking to see if your C compiler knows about "<KEY>"...'
$cat ><KEY>.c <<'EOCP'
main()
{
<KEY> char *foo;
}
EOCP
if $cc -c $ccflags <KEY>.c >/dev/null 2>&1 ; then
val="$define"
echo "Yup, it does."
else
val="$undef"
echo "Nope, it doesn't."
fi
set d_<KEY>
eval $setvar
|
