mirror of
https://github.com/openbsd/src.git
synced 2025-01-10 06:47:55 -08:00
8bad623e4b
Two actively used copies of zlib in base are enough. This simplifies handling security fixes. Now that zlib.h r1.7 is reverted, zlib ffi works fine on 32-bit architectures. Compared with an earlier attempt in March, this disables the Z_SOLO build option (problem found by gkoehler) and fixes two regress tests to work with zlib 1.2.12. Corresponding upstream commits: https://github.com/pmqs/Compress-Raw-Zlib/commit/c44e0b732e214b7f77d42a3af6ae64e https://github.com/pmqs/Compress-Raw-Zlib/commit/f47ea5f36c40fe19efe404dd75fd790 ok bluhm |
||
---|---|---|
.. | ||
gcc | ||
lib | ||
llvm | ||
share | ||
usr.bin | ||
usr.sbin | ||
Makefile | ||
README |
$OpenBSD: README,v 1.2 2016/09/03 22:32:04 benno Exp $ This directory contains software that is Gigantic and Nasty but Unavoidable. Some, but not all, of the software in this subtree follows special rules, i.e. licences other than BSD. So: - check the history of external code before importing it. - for GPL software be ready to arrange for copyright papers somewhat in advance if you want to work on it (the FSF takes a few months to process these). Otherwise, changes might not make it to the main distribution, and may need some further maintenance over time, or risk getting lost. Some internal changes are acceptable, but OpenBSD can't afford to maintain a complete separate toolchain on its own.