Hello! There are still many packages in Debian that fail to build from source on PowerPC targets, both 32-bit and 64-bit big-endian PowerPC, so I thought it might be a good idea to ask the community for help reporting these bugs upstream.
The list of affected packages can be found by following these two links for powerpc and ppc64, respectively: > https://buildd.debian.org/status/architecture.php?a=powerpc&suite=sid > https://buildd.debian.org/status/architecture.php?a=ppc64&suite=sid Look for "Build-Attempted" section and click any of the package names to get to the package's build result overview. Then click onto "Build-Attempted" link in the "Status" column to obtain the build log of a package that failed to build from source (FTBFS), hold the "Ctrl" key to open the build log in a new browser tab. Search the build log for the error, usually by searching for "error:" (the word "error" followed by a colon), in the example of the package "bustools", this looks like this (https://buildd.debian.org/status/fetch.php?pkg=bustools&arch=powerpc&ver=0.42.0%2Bdfsg-1&stamp=1685400928&raw=0): In file included from /<<PKGBUILDDIR>>/src/bustools_clusterhist.cpp:5: /<<PKGBUILDDIR>>/src/Common.hpp: In constructor ‘Bustools_opt::Bustools_opt()’: /<<PKGBUILDDIR>>/src/Common.hpp:111:48: warning: conversion from ‘long long unsigned int’ to ‘size_t’ {aka ‘unsigned int’} changes value from ‘4294967296’ to ‘0’ [-Woverflow] 111 | Bustools_opt() : threads(1), max_memory(1ULL << 32), type(0), | ~~~~~^~~~~ In file included from /<<PKGBUILDDIR>>/src/bustools_collapse.cpp:5: /<<PKGBUILDDIR>>/src/Common.hpp: In constructor ‘Bustools_opt::Bustools_opt()’: /<<PKGBUILDDIR>>/src/Common.hpp:111:48: warning: conversion from ‘long long unsigned int’ to ‘size_t’ {aka ‘unsigned int’} changes value from ‘4294967296’ to ‘0’ [-Woverflow] 111 | Bustools_opt() : threads(1), max_memory(1ULL << 32), type(0), | ~~~~~^~~~~ /<<PKGBUILDDIR>>/src/Common.hpp: In function ‘size_t rndup(size_t)’: /<<PKGBUILDDIR>>/src/Common.hpp:126:10: warning: right shift count >= width of type [-Wshift-count-overflow] 126 | v |= v >> 32; | ~~^~~~~ /<<PKGBUILDDIR>>/src/Common.hpp: In function ‘size_t rndup(size_t)’: /<<PKGBUILDDIR>>/src/Common.hpp:126:10: warning: right shift count >= width of type [-Wshift-count-overflow] 126 | v |= v >> 32; | ~~^~~~~ /<<PKGBUILDDIR>>/src/Common.hpp: At global scope: /<<PKGBUILDDIR>>/src/Common.hpp:132:17: error: redefinition of ‘uint32_t rndup(uint32_t)’ 132 | inline uint32_t rndup(uint32_t v) | ^~~~~ Go back to the other tab which shows the build results for the packages on all architectures, click "Tracker" to get to the package's overview page. Click onto "Homepage" to get to the homepage of the original package and navigate through the webpage to create a bug report. For the bug report, please include: - the full URL to the build log of the affected package on buildd.debian.org - an excerpt from the build log like the one above that shows the actual build error - a mention of the "GCC Compile Farm" (https://gcc.gnu.org/wiki/CompileFarm) explaining that PowerPC machines for debugging the problem on the target architecture can be found there; access to the "GCC Compile Farm" is free for every open source developer Due to the large amount of packages that FTBFS on PowerPC, reporting arch-specific upstream bugs is the perfect task that can be crowd-sourced. In order to avoid redundant bug reports, it's probably a good idea to create a Google Doc sheet to document all packages where a bug report has already been created. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
