BeagleboneA6: Updateing with pacman crippled pacman

[mcc]

Hi,

Just started with ARCHLinux on my Beaglebone and have some trouble...

After preparing a SD card I was able to boot the Beaglebone and login as rpoot via ssh successfully.

As advised as one of the first steps I wanted to update the system (http://archlinuxarm.org/support/guides/ ... irst-steps).

I did a

pacman -Sy openntpd

to install openntpd.

I was asked whether I want to update pacman, for which an newer version was available and I said Yes.
After that procedure, pacman was no longer working due tomissing libaries. Did I bricked my installation?

Thank you very much in advance for any help!

(Below the log)

Have a nice weekend!
Best regards,
mcc

[root@alarm ~]# pacman -Sy openntpd
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
alarm is up to date
aur is up to date
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] Y

resolving dependencies...
looking for inter-conflicts...

Targets (1): pacman-4.0.3-2

Total Download Size: 1.00 MiB
Total Installed Size: 3.38 MiB
Net Upgrade Size: 0.00 MiB

Proceed with installation? [Y/n] Y
:: Retrieving packages from core...
pacman-4.0.3-2-armv7h 1019.5 KiB 173K/s 00:06 [####################################] 100%
(1/1) checking package integrity [####################################] 100%
(1/1) loading package files [####################################] 100%
(1/1) checking for file conflicts [####################################] 100%
(1/1) checking available disk space [####################################] 100%
(1/1) upgrading pacman [####################################] 100%
>>> Run `pacman-key --init` to set up your pacman keyring.
[root@alarm ~]# pacman
pacman: error while loading shared libraries: ld-linux-armhf.so.3: cannot open shared object file: No such file or directory

[pepedog]

:: and upgrade these packages now? [Y/n] Y
Reinstall, next time say no here

[mcc]

Hi,

thank you for your help!

But why should I say no? Is the package itself damaged? Unresolved dependencies?

Best regards,
mcc

[WarheadsSE]

There was an alteration to the naming convention of ld* of the glibc chain thanks to Linaro. That change breaks linking.