Source: bash
Version: 5.3-2
Severity: normal
X-Debbugs-Cc: [email protected]
User: [email protected]
Usertags: sh4

Hi,

the latest upload of bash (5.3-2) is not working correctly on sh4 and causes 
filenames to be
mangled such that other packages are FTBFS or are not built correctly while 
still succeeding.

For example, the libunistring package does not contain correctly named *.so 
files [1]:

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/lib.so.5 -> lib.so.5.2.1
-rw-r--r-- root/root   1969120 2026-03-08 19:19 
./usr/lib/sh4-linux-gnu/lib.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/libunistring5/
-rw-r--r-- root/root       838 2026-03-08 19:19 
./usr/share/doc/libunistring5/changelog.Debian.gz
-rw-r--r-- root/root      4514 2026-02-23 23:11 
./usr/share/doc/libunistring5/changelog.gz
-rw-r--r-- root/root    105103 2026-03-08 19:19 
./usr/share/doc/libunistring5/copyright

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 the 
chroot. I have not yet
figured out whether this issue is a result of miscompilation or a the latest 
patches added to the
bash package.

The broken libunistring package causes gcc-16 to FTBFS on sh4 [2]:

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

I'm building gcc-16 for sh4 manually for now.

I'm filing this bug report for visibility and to document the problem.

Thanks,
Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=libunistring&arch=sh4&ver=1.4.2-1&stamp=1773031590&raw=0
> [2] 
> https://buildd.debian.org/status/fetch.php?pkg=gcc-16&arch=sh4&ver=16-20260308-1&stamp=1773261983&raw=0

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

Reply via email to