[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1115582: bootterm package fails on ppc64le



Thank you Faidon for the info.
The issue is because the functions (which throws error) are defined in <termios.h> and seems like somehow it is not getting added in the source. Currently, this library is added based on the following condition:

#if defined(__linux__) && !defined(NO_TCGETS2)
#include <asm/termbits.h>
#else
#include <termios.h>
#endif

Removing the lib from condition and adding it explicitly gives the error like "error: redefinition of 'struct termios'" because the similar structure also been defined in <termbits.h>. I am trying to check if termbits is required by any of the archs, if not we can remove it, else we can rely on some code tweaks to fix this redifinition error

On 18/09/25 15:50, Faidon Liambotis wrote:
On Thu, Sep 18, 2025 at 03:11:35PM +0530, tshah wrote:
The package fails to build on various architectures. See
https://buildd.debian.org/status/package.php?p=bootterm&suite=sid.
Thank you for your report. Confirmed, although to clarify, it's just
ppc64el that's affected, and it's not a regression (it never worked).
32-bit powerpc is the only other Linux port that is affected, but it's
an unofficial port, as are the Hurd ports.

Able to reproduce the issue while building the package on
pp64el and checked the  build logs from pp64el (https://buildd.debian.org/status/fetch.php?pkg=bootterm&arch=ppc64el&ver=0.5-1&stamp=1744757613&raw=0).
The error seems to be because of some library missiing.
Checking more on this.
I had brought this up with upstream about a year ago. This is about
non-standard custom baud rates and platform differences, on either the
kernel side, glibc side, or both -- that part is unclear to me.

In the time since, glibc 2.41 was released, which includes a news entry
on <termios.h> gaining support for arbitrary baud rates, so perhaps the
right cross-platform fix here is to change the code to rely on that,
instead of using <termbits.h> directly. It needs a bit more research,
and ideally to run this by upstream as well, as I don't have any way to
test this particular functionality. Feel free to take this on, otherwise
I may find some time in the next few months to look at it.

Regards,
Faidon

Reply to: