| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
Backport a patch from upstream to fix symbolization on ppc64, and enable
unit tests on that platform.
|
| |
|
|
|
|
|
| |
136c2572f4d6e6ab8ae02f74d691634874458184 set tests to build in the
`static` directory rather than the `shared` directory. Unfortunately, it
neglected to set the tests to _run_ out of the `static` directory, which
disabled all the tests. Set the tests to run out of `static`.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Abseil 20230125.3 exposes libraries that were formerly internal
(“test-only”) so that other packages’ unit tests can refer to them [1].
Some of the new libraries depend on Google Mock, which Debian only ships
as a static library; as a result, the new libraries can only be shipped
statically as well. Historically, however, Abseil’s Debian packaging has
linked Abseil’s unit tests dynamically to improve build speed. (Google
Mock was built as a one-off shared library during this process, but it
was only ever used in unit tests and was never shipped to users.) Static
Abseil builds were unaware that Google Mock existed, which prevented
sbuild from building the new libraries [2].
To rectify the situation, change Abseil’s Debian packaging to link
Abseil unit tests statically and to ship the new libraries as static
archives. Also make libabsl-dev recommend libgmock-dev, since the new
libraries are useless without a corresponding Google Mock build.
[1] https://github.com/abseil/abseil-cpp/pull/1442
[2] https://bugs.debian.org/1034908
|
| |
|
|
|
| |
Debian’s RISC-V builders don’t have enough resources to run Abseil’s
test suite in parallel. See https://bugs.debian.org/1025221.
|
| |
|
|
|
|
|
| |
Per release-team’s recent request that maintainers support the nocheck
profile <E1oit90-0073rh-LX@respighi.debian.org>, annotate googletest
with <!nocheck> and disable tests in debian/rules if that profile is
set.
|
| |
|
|
|
|
| |
Since upstream commit fb7dd24b18e82893e5922be5d1c8ae0f3fe3c9fa, Abseil
requires both BUILD_TESTING=ON and ABSL_BUILD_TESTING=ON to build unit
tests.
|
| |
|
|
|
|
|
| |
Debian 12’s GCC will default to C++17, so start building Abseil in
C++17 mode. To maximize compatibility, continue to treat absl::any,
absl::optional, absl::string_view, and absl::variant as distinct types
rather than aliases for C++17 types in the std namespace.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Abseil now requires -DBUILD_TESTS=ON instead of -DABSL_RUN_TESTS=ON.
Make the appropriate replacement in debian/rules.
|
| | |
|
| |
|
|
|
|
| |
I’m still working to fix unit tests on non-amd64 platforms, but this
package needs to migrate. Disable unit tests everywhere they don’t
work.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Now that https://bugs.debian.org/970943 has been resolved and a new Git
snapshot of googletest has made it to testing, reenable Abseil unit
tests and run them as part of the build process. This does not change
the package as viewed by dependents; it only provides greater assurance
of correctness when an upload occurs. (It probably would have caught
http://bugs.debian.org/973492, for instance.)
Run the tests against the shared libraries, not the static ones, to
more accurately simulate the conditions under which dependents are
likely to use Abseil.
|
| |
|
|
|
|
|
|
|
|
| |
Remove the symbols file and replace it with an shlibs file. Since Abseil
is almost certain to break ABI with every release, maintaining
fine-grained symbol histories is not terribly useful anyway;
furthermore, since Abseil is a C++ library, maintaining a symbols file
is a lot of work.
Bug: https://bugs.debian.org/966183
|
| |
|
|
|
|
|
|
| |
Rebuild abseil against GCC 9, the version currently in unstable, and
update the symbols file. Additionally, rework the symbols file using
pkg-kde-tools, which offers some automation for building large symbols
files. This does mean that the symbols file now contains mangled names,
but it’s still easily inspected through c++filt.
|
| |
|
|
|
| |
Abseil uses __FILE__ in error messages. Ensure that that macro expands
to the same value on every builder by passing -ffile-prefix-map to GCC.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Build archives in addition to shared objects for Abseil code. Build the
shared objects after the archives so that files autogenerated during
the build (like CMake support files) reference the shared objects, not
the archives. This ensures that users get shared objects by default;
this is the common case in Debian, and it also helps prevent ODR
violations caused by double-linking an archive.
This patch is heavily based on one provided in
<CAKjSHr2qpxgDcnRVoYCptVytTy-QjXy38AM4ppSKv1noXOGjwg@mail.gmail.com>
by László Böszörményi (GCS) <gcs@debian.org>; it’s available on the web
at https://bugs.debian.org/888705#150.
|
| |
|
|
|
|
|
| |
Install Abseil’s CMake support files. Some of these files are
autogenerated, and the generator produces files with a googletest
dependency if Abseil is built with unit tests enabled; to prevent this,
turn off unit tests.
|
|
|
Create basic packaging for Abseil. There’s still work to be done –
there are no autopkgtests, and this package doesn’t install Abseil’s
CMake integration. However, you can install the binary packages and
build programs that link the libraries.
|
Benjamin Barenblat