summaryrefslogtreecommitdiff
path: root/external/bsd/libarchive/lib
AgeCommit message (Collapse)Author
2023-06-03bsd.own.mk: rename GCC_NO_* to CC_WNO_*lukem
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.
2023-05-08Elide OpenSSL-3 deprecation warningchristos
2022-07-22Build and install pkgconfig files for liblzma and libarchivewiz
2021-04-12new GCC_NO_* uses for warning issues. most of the users of the newmrg
GCC_NO_RETURN_LOCAL_ADDR are bugs in GCC itself, not the code.
2020-05-16Add ACL support for FFS. From FreeBSD.christos
2019-10-13introduce some common variables for use in GCC warning disables:mrg
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."
2019-07-24Update build glue and configuration for libarchive 3.4.0.joerg
2019-02-04- use -Wno-error=implicit-fallthrough with GCC7.mrg
2018-02-04switch everyone to openssl.oldchristos
2017-05-21Simplify linking libarchive with libcryptokamil
2017-05-21Remove MKCRYPTO option.riastradh
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.
2017-04-22Obey MKCRYPTO.christos
2017-04-20Update build system for libarchive-3.3.2pre.joerg
2010-11-02Enable direct XZ supportjoerg
2010-02-20Remove a windows-only source file from the list.joerg
2010-02-20Update build infrastructure for libarchive 2.8.0.joerg
2009-01-11bump versions for time_tchristos
2008-09-19Add build glue for libarchive and the frontends. cpio and tar are stilljoerg
disabled.