Building with optimisation results in a make utiliy which fails with
malloc errors when building Git.
It works if no_optimization is used but the problem is specific to
apple-gcc42 build 5553, so I opted to block it off.
Current bottles were built with GCC 4.0.1 on tiger, so leaving them
in place.
Fixes#1513
Any form of compiler optimisation trips up GCC 4.2 whether it's Tigebrew's
default -Os, or libarchive's default of -O2.
Turning off optimisation allows the build to succeed.
Issue observed on Leopard & Snow Leopard. apple-gcc42 on Tiger untested.
On 10.7 & 10.8 it unravels in one of two ways, either libgit.a complaining
about not resolving symbols from OpenSSL, or libicov + some more. I think
the change to build infra that landed in this release is a little premature
and assumes you're not setting LDFLAGS/CFLAGS, and it depends on things
which are set earlier in its build.
Fixes issue #1516
pragma GCC diagnostic not allowed inside functions prior to GCC 4.6.
Patch taken from upstream without changes to tests/ as they're not
built/run here, and m4/curl-compiler.m4 to avoid reconfiguring build
infra.
Fixes issue #1514
Make sure vsnprintf(3) is used as the logic in gzguts.h assumes
that vsnprintf(3) & snprintf(3) were introduced as part of C99 and
not alongside a C89 library.
https://github.com/madler/zlib/pull/1167
Heads up via ZLB-01-001 WP2: Heap Buffer Overflow via Legacy gzprintf Implementation
https://7asecurity.com/reports/pentest-report-zlib-RC1.1.pdf
Enable running the test suite, it should pass fully now.
New version of zpipe.c was published.
v2.1.7 is the last version to support Qt 4.
With v3.0 it switched to Qt 5 and then to 5.5 in subsequent releases.
SDL2 switched to cmake with v2.0.23, and SDL2_sound uses cmake for
build infra, pulling in cmake files SDL2 which our version obviously lacks.
Qt 4 is built without SSL support in Tigerbrew since it only supports the
OpenSSL 1.x API. Qtads by default attempts to connect to sourceforge via HTTP
and expects a 200 responce, but the redirect to HTTPS trips it up, so you're
prompted with an error on launch which you have to click through. We know there
are newer versions! :)