aboutsummaryrefslogtreecommitdiff
path: root/debian/rules
Commit message (Collapse)AuthorAgeFilesLines
* Apply an upstream patch to prevent SIGILLs on RISC-VBenjamin Barenblat2024-03-311-6/+0
| | | | | | | | | Upstream has accepted Aurelien Jarno’s patch removing RISC-V support from unscaledcycleclock. Include it here, fixing https://bugs.debian.org/1059532. Also reenable parallel test runs on RISC-V, per https://bugs.debian.org/1059532#16.
* Fix unit tests on ppc64Benjamin Barenblat2023-08-021-3/+1
| | | | | Backport a patch from upstream to fix symbolization on ppc64, and enable unit tests on that platform.
* Run unit tests out of the `static` directoryBenjamin Barenblat2023-06-271-1/+1
| | | | | | | 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`.
* Package test-only targets as static librariesBenjamin Barenblat2023-05-081-5/+1
| | | | | | | | | | | | | | | | | | | | | 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
* Run tests serially on riscv64Benjamin Barenblat2022-12-051-1/+7
| | | | | Debian’s RISC-V builders don’t have enough resources to run Abseil’s test suite in parallel. See https://bugs.debian.org/1025221.
* Support nocheck profileBenjamin Barenblat2022-10-181-0/+4
| | | | | | | 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.
* Set ABSL_BUILD_TESTINGBenjamin Barenblat2022-08-221-1/+1
| | | | | | Since upstream commit fb7dd24b18e82893e5922be5d1c8ae0f3fe3c9fa, Abseil requires both BUILD_TESTING=ON and ABSL_BUILD_TESTING=ON to build unit tests.
* Build in C++17 modeBenjamin Barenblat2022-08-221-3/+3
| | | | | | | 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.
* Reenable unit tests on hppaBenjamin Barenblat2022-04-141-3/+2
|
* Reenable unit tests on most architecturesBenjamin Barenblat2022-02-041-4/+7
|
* Reenable unit tests on s390xBenjamin Barenblat2022-02-011-1/+1
|
* Reenable unit tests on mips64elBenjamin Barenblat2021-06-131-1/+1
|
* Reenable unit tests on arm64Benjamin Barenblat2021-04-161-3/+1
|
* Request that tests get builtBenjamin Barenblat2021-04-081-1/+1
| | | | | Abseil now requires -DBUILD_TESTS=ON instead of -DABSL_RUN_TESTS=ON. Make the appropriate replacement in debian/rules.
* Reenable unit tests on ppc64elBenjamin Barenblat2021-03-051-1/+5
|
* Re-disable unit tests on non-amd64Benjamin Barenblat2021-01-311-7/+11
| | | | | | 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.
* Avoid OOM on mipsel buildds by disabling unit tests thereBenjamin Barenblat2021-01-311-1/+10
|
* Reenable unit testsBenjamin Barenblat2020-12-011-1/+4
| | | | | | | | | | | | | 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.
* Switch to shlibs infrastructureBenjamin Barenblat2020-07-241-1/+1
| | | | | | | | | | 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
* Rework symbols file for GCC 9 using pkg-kde-toolsBenjamin Barenblat2020-07-231-1/+1
| | | | | | | | 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.
* Pass -ffile-prefix-map during the buildBenjamin Barenblat2020-05-221-1/+1
| | | | | 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 static librariesBenjamin Barenblat2020-05-221-2/+12
| | | | | | | | | | | | | | 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.
* Enable CMake supportBenjamin Barenblat2020-05-191-1/+1
| | | | | | | 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.
* Start packaging AbseilBenjamin Barenblat2020-05-181-0/+26
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.
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-10 22:59:31 +0000