[ ok ] * Running 'autoconf --force' ... [ ok ] * Running 'automake --add-missing --copy --foreign --force-missing' ... [ !! ] * Failed running 'automake'! * * Include in your bug report the contents of: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_systemd-20240710-124502 UNMASKED: Requested by sam ~dev-libs/icu-75.1 ~dev-libs/icu-layoutex-75.1 Requested by dilfridge and sam ~dev-lang/perl-5.40.0 ~virtual/perl-Archive-Tar-3.20.10_rc ~virtual/perl-CPAN-Meta-Requirements-2.143.0 ~virtual/perl-Compress-Raw-Bzip2-2.212.0 ~virtual/perl-DB_File-1.859.0 ~virtual/perl-Data-Dumper-2.189.0 ~virtual/perl-Devel-PPPort-3.720.0 ~virtual/perl-Exporter-5.780.0 ~virtual/perl-ExtUtils-CBuilder-0.280.240 ~virtual/perl-ExtUtils-Manifest-1.750.0 ~virtual/perl-File-Spec-3.900.0 ~virtual/perl-HTTP-Tiny-0.88.0 ~virtual/perl-IO-1.550.0 ~virtual/perl-IO-Compress-2.212.0 ~virtual/perl-IO-Socket-IP-0.420.0 ~virtual/perl-IO-Zlib-1.150.0 ~virtual/perl-Math-BigInt-2.3.2 ~virtual/perl-Math-BigInt-FastCalc-0.501.800 ~virtual/perl-Math-BigRat-2.3.2 ~virtual/perl-Module-CoreList-5.202.406.90 ~virtual/perl-Module-Metadata-1.0.38 ~virtual/perl-Pod-Simple-3.450.0 ~virtual/perl-Safe-2.460.0 ~virtual/perl-Socket-2.38.0 ~virtual/perl-Test-Harness-3.480.0 ~virtual/perl-Test-Simple-1.302.199 ~virtual/perl-Text-Tabs+Wrap-2024.1.0 ~virtual/perl-Time-HiRes-1.977.700 ~virtual/perl-Time-Local-1.350.0 ~virtual/perl-autodie-2.370.0 ~virtual/perl-bignum-0.670.0 ~virtual/perl-podlators-5.10.200_rc ~virtual/perl-threads-2.400.0 ~virtual/perl-threads-shared-1.690.0 ~virtual/perl-version-0.993.0 The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10 [2] x86_64-pc-linux-gnu-14 * clang/llvm (if any): clang version 18.1.8 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/18/bin Configuration file: /etc/clang/x86_64-pc-linux-gnu-clang.cfg /usr/lib/llvm/18 18.1.8 Python 3.12.4 Available Ruby profiles: [1] ruby31 (with Rubygems) [2] ruby32 (with Rubygems) [3] ruby33 (with Rubygems) * Available Rust versions: [1] rust-bin-1.79.0 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 11.0.23_p9 [openjdk-bin-11] 2) Eclipse Temurin JDK 17.0.11_p9 [openjdk-bin-17] *) Eclipse Temurin JDK 21.0.3_p9 [openjdk-bin-21] 4) Eclipse Temurin JDK 8.412_p08 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 [3] openjdk-bin-17 [4] openjdk-bin-21 system-vm The Glorious Glasgow Haskell Compilation System, version 9.2.8 php cli (if any): go version go1.22.5 linux/amd64 HEAD of ::gentoo commit dbfdbe5e386bee5a6f6a9c2e07d8d03973b6148f Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Wed Jul 17 00:04:04 2024 +0000 2024-07-17 00:04:04 UTC emerge -qpvO net-dns/ddclient [ebuild N ] net-dns/ddclient-3.11.2 USE="-examples (-selinux) -test"
Created attachment 897847 [details] emerge-info.txt
Created attachment 897848 [details] emerge-history.txt.xz
Created attachment 897849 [details] environment
Created attachment 897850 [details] etc.clang.tar.xz
Created attachment 897851 [details] etc.portage.tar.xz
Created attachment 897852 [details] net-dns:ddclient-3.11.2:20240717-010642.log
Created attachment 897853 [details] qlist-info.txt.xz
Created attachment 897854 [details] temp.tar.xz
Upstream bug: https://github.com/ddclient/ddclient/issues/745 Temporary (in my opinion) fix: https://github.com/ddclient/ddclient/commit/9eb4558772b84516363c960fe53c014575d80df9.patch This fix is proposed as part of an unmerged PR that just disables treating warnings as errors. If your system is one of those with portability problems then you need to look into fixing the Makefile.am: https://github.com/ddclient/ddclient/pull/746 To apply this, you can just create a directory /etc/portage/patches/net-dns/ddclient-3.11.2 and download the above patch into it. I called the file configure.ac.patch. Portage is clever enough to pick up user patches and apply them. This is not a proper solution, but given the time that we have this breaking change on the upstream package without a fix, I would consider hard masking this version until a better fix is available.
