| History log of /src/external/bsd/am-utils/bin/amd/Makefile |
| Revision | | Date | Author | Comments |
| 1.15 |
| 03-Jun-2023 |
lukem | bsd.own.mk: rename GCC_NO_* to CC_WNO_*
Rename compiler-warning-disable variables from
GCC_NO_warning
to
CC_WNO_warning
where warning is the full warning name as used by the compiler.
GCC_NO_IMPLICIT_FALLTHRU is CC_WNO_IMPLICIT_FALLTHROUGH
Using the convention CC_compilerflag, where compilerflag
is based on the full compiler flag name.
|
| 1.14 |
| 14-Aug-2021 |
christos | Adjust for new OpenLDAP
- use centralized library variables
- ldap_connect -> ldap_xconnect
|
| 1.13 |
| 13-Oct-2019 |
mrg | introduce some common variables for use in GCC warning disables:
GCC_NO_FORMAT_TRUNCATION -Wno-format-truncation (GCC 7/8)
GCC_NO_STRINGOP_TRUNCATION -Wno-stringop-truncation (GCC 8)
GCC_NO_STRINGOP_OVERFLOW -Wno-stringop-overflow (GCC 8)
GCC_NO_CAST_FUNCTION_TYPE -Wno-cast-function-type (GCC 8)
use these to turn off warnings for most GCC-8 complaints. many
of these are false positives, most of the real bugs are already
commited, or are yet to come.
we plan to introduce versions of (some?) of these that use the
"-Wno-error=" form, which still displays the warnings but does
not make it an error, and all of the above will be re-considered
as either being "fix me" (warning still displayed) or "warning
is wrong."
|
| 1.12 |
| 21-May-2017 |
riastradh | branches: 1.12.10;
Remove MKCRYPTO option.
Originally, MKCRYPTO was introduced because the United States
classified cryptography as a munition and restricted its export. The
export controls were substantially relaxed fifteen years ago, and are
essentially irrelevant for software with published source code.
In the intervening time, nobody bothered to remove the option after
its motivation -- the US export restriction -- was eliminated. I'm
not aware of any other operating system that has a similar option; I
expect it is mainly out of apathy for churn that we still have it.
Today, cryptography is an essential part of modern computing -- you
can't use the internet responsibly without cryptography.
The position of the TNF board of directors is that TNF makes no
representation that MKCRYPTO=no satisfies any country's cryptography
regulations.
My personal position is that the availability of cryptography is a
basic human right; that any local laws restricting it to a privileged
few are fundamentally immoral; and that it is wrong for developers to
spend effort crippling cryptography to work around such laws.
As proposed on tech-crypto, tech-security, and tech-userlevel to no
objections:
https://mail-index.netbsd.org/tech-crypto/2017/05/06/msg000719.html
https://mail-index.netbsd.org/tech-security/2017/05/06/msg000928.html
https://mail-index.netbsd.org/tech-userlevel/2017/05/06/msg010547.html
P.S. Reviewing all the uses of MKCRYPTO in src revealed a lot of
*bad* crypto that was conditional on it, e.g. DES in telnet... That
should probably be removed too, but on the grounds that it is bad,
not on the grounds that it is (nominally) crypto.
|
| 1.11 |
| 25-Jan-2015 |
christos | new lex/yacc need less help with prefixes.
|
| 1.10 |
| 14-Feb-2013 |
christos | add PROGDPLIBS, and remove duplicate dependencies.
|
| 1.9 |
| 17-Aug-2011 |
christos | branches: 1.9.2; 1.9.8;
fix aliasing issues and remove gcc hacks.
|
| 1.8 |
| 22-Jun-2011 |
mrg | apply some -Wno-error and/or -fno-strict-aliasing.
all of this should be looked at closer, but some of them are not
very trivial.
|
| 1.7 |
| 20-Jun-2011 |
mrg | remove most of the remaining HAVE_GCC tests that are always true in
the modern world.
|
| 1.6 |
| 26-May-2011 |
joerg | branches: 1.6.2;
Default to -Wno-sign-compare -Wno-pointer-sign for clang.
Push -Wno-array-bounds down to the cases that depend on it.
Selectively disable warnings for 3rd party software or non-trivial
issues to be reviewed later to get clang -Werror to build most of the
tree.
|
| 1.5 |
| 08-Feb-2010 |
plunky | use
.if defined(HAVE_GCC) && ${HAVE_GCC} == 4
rather than
.if ${HAVE_GCC} == 4
as HAVE_GCC may be undefined
|
| 1.4 |
| 29-Oct-2009 |
christos | no need for YY_NO here.
|
| 1.3 |
| 20-Apr-2009 |
drochner | define YY_NO_INPUT where appropriate, from Kurt J. Lidl per PR misc/41160
|
| 1.2 |
| 20-Mar-2009 |
christos | need udf.
|
| 1.1 |
| 19-Sep-2008 |
christos | branches: 1.1.4; 1.1.8;
resolve issues and add build glue
|
| 1.1.8.1 |
| 13-May-2009 |
jym | Sync with HEAD.
Second commit. See http://mail-index.netbsd.org/source-changes/2009/05/13/msg221222.html
|
| 1.1.4.2 |
| 19-Oct-2008 |
haad | Sync with HEAD.
|
| 1.1.4.1 |
| 19-Sep-2008 |
haad | file Makefile was added on branch haad-dm on 2008-10-19 22:39:28 +0000
|
| 1.6.2.1 |
| 23-Jun-2011 |
cherry | Catchup with rmind-uvmplock merge.
|
| 1.9.8.1 |
| 25-Feb-2013 |
tls | resync with head
|
| 1.9.2.1 |
| 22-May-2014 |
yamt | 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")
|
| 1.12.10.1 |
| 13-Apr-2020 |
martin | Mostly merge changes from HEAD upto 20200411
|
