6be406e820
Turn off -fno-strict-aliasing for HAVE_GCC; it makes no difference to
...
the compiler output and is therefore ipso facto not necessary. I'll
leave it on for HAVE_LLVM as I can't check that tonight.
(If there is invalid code in here that actually requires it, let me
know so I can fix things properly.)
2013-08-11 03:49:24 +00:00
9edf9a0457
Remove many HAVE_GCC || HAVE_PCC conditionals as the options also apply
...
to Clang. Add a few cases of HAVE_LLVM for -fno-strict-aliasing.
2012-08-10 12:10:27 +00:00
75e42fa7da
remove most of the remaining HAVE_GCC tests that are always true in
...
the modern world.
2011-06-20 07:43:56 +00:00
d877c4c3c0
Enable WARNS=4 by default, except for:
...
cpuctl dumplfs hprop ipf iprop-log kadmin kcm kdc kdigest
kimpersonate kstash ktutil makefs ndbootd ntp pppd quot
racoon racoonctl rtadvd sntp sup tcpdchk tcpdmatch tcpdump
traceroute traceroute6 user veriexecgen wsmoused zic
(Mostly third-party applications)
2009-04-22 15:23:01 +00:00
3c9a95916d
Wrap compiler-specific flags with HAVE_GCC and HAVE_PCC as necessary. Add a few flags for PCC.
2008-08-29 00:02:21 +00:00
aadd7d4847
sprinkle some -fno-strict-aliasing and -Wno-pointer-sign with GCC4.
2006-05-11 23:16:28 +00:00
17d72c8a6b
use NETBSDSRCDIR as appropriate
2002-09-18 03:54:26 +00:00
e5bc90f40c
Merge with Lite2 + local changes
1998-03-01 02:20:01 +00:00
f5bf267d90
enable WARNS=1 by default, but disable in unclean 3rd party code
1997-10-18 06:42:25 +00:00
10e180cc49
Back out the .PATH.c changes. The .depend problem (and others)
...
will be fixed using the new .NOPATH make feature instead.
1997-05-08 21:11:01 +00:00
012e528f2e
Use .PATH.c: ...
1997-05-06 20:44:56 +00:00
0114e805ce
convert to new RCS Id conventions; reduce my headache
1995-03-18 14:54:19 +00:00
06e2955ff1
specify man pages the new way.
1994-12-22 10:44:04 +00:00
48c91e8043
do not need -I/sys
1994-08-03 21:07:10 +00:00
928beac1da
X compilation
1994-06-10 17:33:55 +00:00
ccfa3742b5
Update from 4.4-Lite, with local changes.
1994-06-08 18:57:30 +00:00
dholland