bash violates FHS

[ticpu]

Bash violates file system hierarchy standards by being in /bin and depending on libgcc_s which is in /usr. This should get fixed.

root ~ # ldd /bin/bash
libreadline.so.6 => /lib/libreadline.so.6 (0x4011e000)
libhistory.so.6 => /lib/libhistory.so.6 (0x40057000)
libncursesw.so.5 => /lib/libncursesw.so.5 (0x40076000)
libdl.so.2 => /lib/libdl.so.2 (0x40034000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x4000f000)
libc.so.6 => /lib/libc.so.6 (0x40159000)
/lib/ld-linux.so.3 (0x400f7000)

[WarheadsSE]

I blame upstream.

[kmihelich]

We don't write the packages (except for a few), we just compile them for ARM. If this is something that goes against Arch policies, write a thorough bug report on their tracker.

[ticpu]

$this->bbcode_second_pass_quote('WarheadsSE', 'I') blame upstream.

[kmihelich]

Our bash package was compiled May 10, which was before I switched all of the builders to a clean chroot build system. It's possibly just a product of the previous way I built packages.

[ticpu]

I just did makepkg on bash from core/bash on packages.archlinux.org and it still compiles against libgcc_s, I'll do some checks to see why it happens on ARM.

[ticpu]

Adding -static-libgcc to the final bash link makes bash bigger as expected and patches the problem.

Could it be that ARM has some missing mathematical features imported from libgcc ?
I see it could be thread support here: http://minimalinux.org/forum/viewtopic.php?id=483

root ~/aur/bash/src/bash-4.2 $ ls -l ../../pkg/bin/bash bash
-rwxr-xr-x 1 root root 738249 Sep 11 16:04 bash
-rwxr-xr-x 1 root root 603336 Sep 11 15:26 ../../pkg/bin/bash

[kmihelich]

Actually, if it's a serious issue that needs to be addressed, send it to Arch. Be sure there is something explicit here https://wiki.archlinux.org/index.php/Fi ... y_Standard that is with your complaint.

If the binary referencing something in some other directory is just a pet peeve, I'm not going to maintain another package in git just because of it. In all honesty, there are far larger issues than where files end up or what they reference.

[ticpu]

The issue is that if you mount /usr later in the boot process, you're doomed to total failure of all scripts depending on /bin/bash, which is almost everything in ArchLinux as there is no /bin/dash or any alternative.

Edit: Correction, I just checked for installing dash and it is present by default, so linking /bin/sh to /bin/dash would correct boot problems without /usr mounted if all scripts point to /bin/sh, I'll try this out.

[kmihelich]

I would wager that I could represent on one hand the amount of people that run this distribution with a root filesystem that fragmented between different partitions. I figured that practice had gone out a long time ago, and haven't seen anyone bother with it in many many years.