[Debian-lego-team] h8300 Toolchain Rebuild Failure Notice

[Nicolas Schodet]

* Matthew Sheets <ms.github at outlook.com> [2025-09-06 14:08]:
> I saw the recent build failure notifications for binutils-h8300-hms and gcc-h8300-hms due to errors encountered "during a rebuild of all packages in unstable."
>  * binutils - https://people.debian.org/~sanvila/build-logs/202509/binutils-h8300-hms_2.16.1-13_amd64-20250904T164016.670Z
>  * gcc - https://people.debian.org/~sanvila/build-logs/202509/gcc-h8300-hms_3.4.6+dfsg2-7_amd64-20250904T200953.138Z

> I have not yet seen this error triggered on the weekly GitHub Action I have setup [1], but in poking around, it appears a patch might have been submitted back in 2005 that would address this.
>  [1] https://github.com/BrickBot/GNU-Legacy-Toolchain/actions
>  [2] https://gcc.gnu.org/legacy-ml/gcc-patches/2005-05/msg01513.html
>       - Note also the follow-up email

> In comparing libiberty in binutils-2.16.1 vs gcc-4.4.7, it appears some changes were indeed applied in that regard.
>  * https://github.com/BrickBot/GNU-Legacy-Toolchain/blob/master/src-projects/binutils-2.16.1/libiberty/getpwd.c#L42
>  * https://github.com/BrickBot/GNU-Legacy-Toolchain/blob/master/src-projects/gcc-4.4.7/libiberty/getpwd.c#L49

> I will need to dig into this a little bit further yet but wanted to go ahead and pass along what I have found thus far.

Good find, I can take this patch.

I am not too woried, libiberty main goal is to support all kind of
old unixes, but we only need to support Debian build, so our life is
simpler.

Kind regard,

Nicolas.