Re: Bug#1130485: bash: Filenames being mangled on sh4 cause other packages to FTBFS

--=-OKSyP1F/Mo4dhSmD6OO3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Control: tags -1 +patch

Hi,

On Thu, 2026-03-12 at 13:32 +0100, John Paul Adrian Glaubitz wrote:
> the latest upload of bash (5.3-2) is not working correctly on sh4 and cau=
ses filenames to be
> mangled such that other packages are FTBFS or are not built correctly whi=
le still succeeding.
>=20
> For example, the libunistring package does not contain correctly named *.=
so files [1]:
>=20
> drwxr-xr-x root/root         0 2026-03-08 19:19 ./
> drwxr-xr-x root/root         0 2026-03-08 19:19 ./usr/
> drwxr-xr-x root/root         0 2026-03-08 19:19 ./usr/lib/
> drwxr-xr-x root/root         0 2026-03-08 19:19 ./usr/lib/sh4-linux-gnu/
> lrwxrwxrwx root/root         0 2026-03-08 19:19 ./usr/lib/sh4-linux-gnu/l=
ib.so.5 -> lib.so.5.2.1
> -rw-r--r-- root/root   1969120 2026-03-08 19:19 ./usr/lib/sh4-linux-gnu/l=
ib.so.5.2.1
> drwxr-xr-x root/root         0 2026-03-08 19:19 ./usr/share/
> drwxr-xr-x root/root         0 2026-03-08 19:19 ./usr/share/doc/
> drwxr-xr-x root/root         0 2026-03-08 19:19 ./usr/share/doc/libunistr=
ing5/
> -rw-r--r-- root/root       838 2026-03-08 19:19 ./usr/share/doc/libunistr=
ing5/changelog.Debian.gz
> -rw-r--r-- root/root      4514 2026-02-23 23:11 ./usr/share/doc/libunistr=
ing5/changelog.gz
> -rw-r--r-- root/root    105103 2026-03-08 19:19 ./usr/share/doc/libunistr=
ing5/copyright
>=20
> The filename of "libunistring.so.5" was mangled to "lib.so.5". I was able=
 to fix the libunistring
> package by rebuilding the package manually with bash_5.3-1 installed in t=
he chroot. I have not yet
> figured out whether this issue is a result of miscompilation or a the lat=
est patches added to the
> bash package.
>=20
> The broken libunistring package causes gcc-16 to FTBFS on sh4 [2]:
>=20
> msgfmt -o de.mo ../../../../src/libstdc++-v3/po/de.po
> msgfmt -o fr.mo ../../../../src/libstdc++-v3/po/fr.po
> /usr/bin/msgfmt: error while loading shared libraries: libunistring.so.5:=
 cannot open shared object file: No such file or directory
> /usr/bin/msgfmt: error while loading shared libraries: libunistring.so.5:=
 cannot open shared object file: No such file or directory
>=20
> I'm building gcc-16 for sh4 manually for now.
>=20
> I'm filing this bug report for visibility and to document the problem.

Building bash with -O1 on sh4 (see attached patch) seems to fix the issue.
I will need to perform some more tests to verify this theory though, but
I think we can just apply the patch to be safe for the time being.

Adrian

--=20
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

--=-OKSyP1F/Mo4dhSmD6OO3
Content-Disposition: attachment; filename="bash-sh4-o1.diff"
Content-Transfer-Encoding: base64
Content-Type: text/x-patch; name="bash-sh4-o1.diff"; charset="UTF-8"

LS0tIGRlYmlhbi9ydWxlcy5vcmlnCTIwMjUtMDEtMjEgMTQ6MzM6NDUuMDAwMDAwMDAwICswMTAw
CisrKyBkZWJpYW4vcnVsZXMJMjAyNi0wNS0wMSAxMDo0NzoxMC40MzcwMDc5MTcgKzAyMDAKQEAg
LTQ2LDYgKzQ2LDEyIEBACiBDUFBGTEFHUyA6PSAkKHNoZWxsICQoZHBrZ19idWlsZGZsYWdzKSAt
LWdldCBDUFBGTEFHUykKIExERkxBR1MgOj0gJChzaGVsbCAkKGRwa2dfYnVpbGRmbGFncykgLS1n
ZXQgTERGTEFHUykKIAorIyBTZWU6IGh0dHBzOi8vYnVncy5kZWJpYW4ub3JnL2NnaS1iaW4vYnVn
cmVwb3J0LmNnaT9idWc9MTEzMDQ4NQoraWZuZXEgKCwkKGZpbHRlciAkKERFQl9IT1NUX0FSQ0gp
LHNoNCkpCisgIENGTEFHUyA6PSAkKENGTEFHUzotTzI9LU8xKQorICBDWFhGTEFHUyA6PSAkKENY
WEZMQUdTOi1PMj0tTzEpCitlbmRpZgorCiBTSEVMTAk9IC9iaW4vYmFzaAogWUFDQwk9IGJpc29u
IC15CiAK


--=-OKSyP1F/Mo4dhSmD6OO3--