Compile and install software

I need the new compression utility compiled and installed on the build farm. Pull version 2.4.1 source from the upstream tarball, compile with optimizations for x86_64, run the unit tests, install into /usr/local, update the symlink so the system uses the new binary, and verify the md5sum matches the artifact we built. Do those steps on build1 and build2 and report any test failures.

Before I build and install this on the fleet, make the package easy for reviewers. Put the compile flags and target architecture up front, list test failures and how to reproduce them locally, make the install path and symlink change obvious, and flag any ABI or library version changes that would make a reviewer hesitate to upgrade on the build farm.

I built and installed version 2.4.1 on build1; compile logs look clean and unit tests passed, but the binary crashes with a segmentation fault on startup. The QA lead expects a stable build for tomorrow; I do not know whether this is due to missing runtime libraries, optimization flags, or an untested code path. What is the most likely diagnosis and the fastest, least disruptive step to get a working binary for QA tonight?

Over the last quarter we repeatedly produce builds that pass unit tests but fail immediately in production or QA with runtime errors. Each time we chase environment differences and waste days. Where are we repeatedly making the same mistake, and what single practice change would catch these runtime regressions before a release goes out?