Yep, it looks like the whole system is corrupted by probably breaking up during the upgrade process when a problem occurs with DNS resolution I suspect but please correct me, if I am wrong.
[pi@raspi]$ rpm -q libstdc++
libstdc++-8.3.1-2.fc29.aarch64
libstdc++-9.0.1-0.10.fc30.aarch64
[pi@raspi]$ sudo rpm -V libstdc++-9.0.1-0.10.fc30.i686.rpm
Unsatisfied dependencies for libstdc++-9.0.1-0.10.fc30.i686:
ld-linux.so.2 is needed by libstdc++-9.0.1-0.10.fc30.i686
ld-linux.so.2(GLIBC_2.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6 is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.1) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.1.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.16) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.17) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.18) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.2) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.3.2) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.4) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.6) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1 is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GCC_3.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GCC_3.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GCC_3.4) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GCC_4.2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
libm.so.6 is needed by libstdc++-9.0.1-0.10.fc30.i686
libm.so.6(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
missing a /usr/lib/.build-id/ba/a735e48f9645a7e5bef8b869cd9b61d81e894a
missing /usr/lib/libstdc++.so.6
missing /usr/lib/libstdc++.so.6.0.26
S.5...... /usr/share/gcc-9/python/libstdcxx/__init__.py
S.5....T. /usr/share/gcc-9/python/libstdcxx/__pycache__/__init__.cpython-37.opt-1.pyc
S.5....T. /usr/share/gcc-9/python/libstdcxx/__pycache__/__init__.cpython-37.pyc
S.5...... /usr/share/gcc-9/python/libstdcxx/v6/__init__.py
S.5....T. /usr/share/gcc-9/python/libstdcxx/v6/__pycache__/__init__.cpython-37.opt-1.pyc
S.5....T. /usr/share/gcc-9/python/libstdcxx/v6/__pycache__/__init__.cpython-37.pyc
S.5....T. /usr/share/gcc-9/python/libstdcxx/v6/__pycache__/printers.cpython-37.opt-1.pyc
S.5....T. /usr/share/gcc-9/python/libstdcxx/v6/__pycache__/printers.cpython-37.pyc
S.5....T. /usr/share/gcc-9/python/libstdcxx/v6/__pycache__/xmethods.cpython-37.opt-1.pyc
S.5....T. /usr/share/gcc-9/python/libstdcxx/v6/__pycache__/xmethods.cpython-37.pyc
S.5...... /usr/share/gcc-9/python/libstdcxx/v6/printers.py
S.5...... /usr/share/gcc-9/python/libstdcxx/v6/xmethods.py
missing /usr/share/gdb/auto-load/usr/lib
missing /usr/share/gdb/auto-load/usr/lib/__pycache__
missing /usr/share/gdb/auto-load/usr/lib/__pycache__/libstdc++.so.6.0.26-gdb.cpython-37.opt-1.pyc
missing /usr/share/gdb/auto-load/usr/lib/__pycache__/libstdc++.so.6.0.26-gdb.cpython-37.pyc
missing /usr/share/gdb/auto-load/usr/lib/libstdc++.so.6.0.26-gdb.py
On Wed, May 1, 2019 at 10:24 PM Pavel Holica <conscript89@xxxxxxxxx> wrote:
You should download aarch64 one and the same version as the rpm -q libstdc++ tells. The correct rpm should have the dependencies resolved.It seem the library file is corrupted. To see all the corrupted files you can also run rpm -Va (or just rpm -V package_name) to see if this is only isolated issue or if it's system wide.st 1. 5. 2019 v 22:20 odesílatel <ng0177@xxxxxxxxx> napsal:I tried this but too many dependencies, see below. Maybe that whole issue is related to using the Pi3 as a DNS resolver at the same time when upgrading although plain updating works very well. Can anyone point me to the right log files to look at. journalctl is inconclusive (to me)? Appreciate.[pi@raspi]$ sudo rpm -Uvh libstdc++-9.0.1-0.10.fc30.i686.rpmerror: Failed dependencies:ld-linux.so.2 is needed by libstdc++-9.0.1-0.10.fc30.i686ld-linux.so.2(GLIBC_2.3) is needed by libstdc++-9.0.1-0.10.fc30.i686libc.so.6 is needed by libstdc++-9.0.1-0.10.fc30.i686libc.so.6(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686libc.so.6(GLIBC_2.1) is needed by libstdc++-9.0.1-0.10.fc30.i686libc.so.6(GLIBC_2.1.3) is needed by libstdc++-9.0.1-0.10.fc30.i686libc.so.6(GLIBC_2.16) is needed by libstdc++-9.0.1-0.10.fc30.i686libc.so.6(GLIBC_2.17) is needed by libstdc++-9.0.1-0.10.fc30.i686libc.so.6(GLIBC_2.18) is needed by libstdc++-9.0.1-0.10.fc30.i686libc.so.6(GLIBC_2.2) is needed by libstdc++-9.0.1-0.10.fc30.i686libc.so.6(GLIBC_2.3) is needed by libstdc++-9.0.1-0.10.fc30.i686libc.so.6(GLIBC_2.3.2) is needed by libstdc++-9.0.1-0.10.fc30.i686libc.so.6(GLIBC_2.4) is needed by libstdc++-9.0.1-0.10.fc30.i686libc.so.6(GLIBC_2.6) is needed by libstdc++-9.0.1-0.10.fc30.i686libgcc_s.so.1 is needed by libstdc++-9.0.1-0.10.fc30.i686libgcc_s.so.1(GCC_3.0) is needed by libstdc++-9.0.1-0.10.fc30.i686libgcc_s.so.1(GCC_3.3) is needed by libstdc++-9.0.1-0.10.fc30.i686libgcc_s.so.1(GCC_3.4) is needed by libstdc++-9.0.1-0.10.fc30.i686libgcc_s.so.1(GCC_4.2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686libgcc_s.so.1(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686libm.so.6 is needed by libstdc++-9.0.1-0.10.fc30.i686libm.so.6(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686_______________________________________________On Wed, May 1, 2019 at 9:04 PM Tom Callaway <tcallawa@xxxxxxxxxx> wrote:ImportError: /lib64/libstdc++.so.6: file too short^^^ This is the core problem. Try downloading the libstdc++ package manually and reinstalling it with rpm.~tom
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
--Pavel Holica
_______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx