[solved] libicui18n.so.64 missing

sukolyn · 2020-01-28 22:02:00

hi,

chromium complains about missing libicui18n.so.64 :

/usr/lib/chromium/chromium: error while loading shared libraries: libicui18n.so.64: cannot open shared object file: No such file or directory

this would probably impact other programs that I don't use.

pacman -Qi chromium
returns
74.0.3729.169-2.0
as version.

do you need any other informations ?

Last edited by sukolyn (2020-01-31 15:04:31)

levi · 2020-01-28 22:42:28

Yes icu is too new for your chromium. I currently have libicui18n.so.65 from icu 65.1-2.0.

I'll note my repos say that chromium 79.0.3945.117-1.0 is available, so you're a bit behind.

sukolyn · 2020-01-29 15:09:56

what are your repos address?
I only use french one. is there any difference from one to the others? how to tell which one is the more up to date?

abaumann · 2020-01-29 18:04:02

You can see the status of each mirror on https://www.archlinux32.org/mirrors/status/

sukolyn · 2020-01-29 18:33:32

thank you.

I updated system (pacman -Syu), but pacman -Qi chromium still shows 74.0.379 version.

another computer, with 64bits Archlinux installed, chromium is indeed 79.0.3945

levi · 2020-01-29 21:25:52

What's your topline mirrolist selection? Mine is mirror.archlinux32.org in Germany and seems to include the same version of chromium as upstream. Seems whichever repo you're using is lagging, and there are a couple of relatively famous repos that are lagging in that mirror status page above although I'm not sure what the units are there. Assuming they're seconds, the biggest one only counts for under 4 hours of lag. I'm guessing therefore that mirror status page doens't flag up out of date packages.

The two repos officially flagged as french that are at agoctrl.org have the biggest delay thouguh, so maybe actually it's not seconds. If it were hours instead, then that would be a lag of a couple of months.

Last edited by levi (2020-01-29 21:28:39)

sukolyn · 2020-01-29 23:50:02

here's mirrorlist after rankmirrors (which doesn't tell how mirror is up to date only how quick they're reachable, but I guess andreasbaumann.cc is )

Server = http://ger.mirror.archlinux32.org/$arch/$repo
Server = http://archlinux32.andreasbaumann.cc/$arch/$repo
Server = https://ger.mirror.archlinux32.org/$arch/$repo
Server = http://de.mirror.archlinux32.org/$arch/$repo
Server = http://mirror.math.princeton.edu/pub/archlinux32/$arch/$repo
Server = https://mirror.archlinux32.org/$arch/$repo
Server = https://de.mirror.archlinux32.org/$arch/$repo
Server = https://archlinux32.andreasbaumann.cc/$arch/$repo
Server = https://archlinux32.agoctrl.org/$arch/$repo
Server = http://sgp.mirror.archlinux32.org/$arch/$repo
Server = http://mirror.datacenter.by/pub/archlinux32/$arch/$repo
Server = http://archlinux32.agoctrl.org/$arch/$repo
Server = http://ind.mirror.archlinux32.org/$arch/$repo
Server = https://mirror.math.princeton.edu/pub/archlinux32/$arch/$repo
Server = https://32.arlm.tyzoid.com/$arch/$repo
Server = https://sgp.mirror.archlinux32.org/$arch/$repo
Server = http://mirror.yandex.ru/archlinux32/$arch/$repo
Server = https://mirror.yandex.ru/archlinux32/$arch/$repo
Server = https://mirror.datacenter.by/pub/archlinux32/$arch/$repo
Server = http://mirror.archlinux32.org/$arch/$repo
Server = https://jpn.mirror.archlinux32.org/$arch/$repo
Server = http://jpn.mirror.archlinux32.org/$arch/$repo
Server = https://ind.mirror.archlinux32.org/$arch/$repo
Server = http://mirror.archlinux32.oss/$arch/$repo

no changes, though.

Last edited by sukolyn (2020-01-29 23:52:10)

abaumann · 2020-01-30 07:24:23

pacman-conf Architecture
pentium4

Server = http://archlinux32.andreasbaumann.cc/$arch/$repo

pacman -Ss chromium
extra/chromium 79.0.3945.117-1.0

on i686:
extra/chromium 74.0.3729.169-2.0 [installed]

So you are on i686. :-)

Chances are, that your CPU has SSE2 (please check the flags in /proc/cpuinfo).
If yes, do a migration to pentium4 as chromium is micro-optimized and will probably
not build for i686 without investing tremendous amounts of testing (and some hair pulling).

See https://bbs.archlinux32.org/viewtopic.php?pid=12

sukolyn · 2020-01-30 17:09:47

good guess : i686, and SSE2.

I pretty sure I can't change CPU as it is a tiny HP T5455.

it's not a big deal anyway,
I usually use this machine as a vnc client.
some times I just don't need to wake the server.
I'll go for a more lightweight web browser.

Thank you for maintaining 32 bits version.

abaumann · 2020-01-30 19:23:14

What I mean is, do the Archlinux32 architecture transition to 'pentium4', if your CPU has SSE2.
I was not suggesting to swap the metal version of the CPU. :-)

sukolyn · 2020-01-30 20:21:07

silly me.

sukolyn · 2020-01-30 20:40:01

/etc/pacman.conf Architecture=auto, though.

I changed to pentium4, and change appears : available version of chromium is now 79...

update in progress . . .

levi · 2020-01-30 20:46:34

Ah, that's a good spot. I'd completely forgotten that there was more than my platform when checking for versions and should have checked the others (well maybe not i486 - unless the OP indicated using something really old or odd). I wonder what the blocker is on chromium for i686?

Edit: If the architeture in pacman.conf was set to auto, and it was updated, yet it still wasn't picking pentium4 packages, I'd assume it has some reason for that. I'd assume installing pentium4 packages on such a machine it likely to be problematic, although I don't know if such a machine would even boot to be fair.

Last edited by levi (2020-01-30 20:50:36)

abaumann · 2020-01-31 07:07:51

@sukolyn: the Architecture=auto somes doesn't work for unknown reasons to check for SSE2 in the Archlinux32 fork of the pacman binary.
@levi: SSE2 optimizations everywhere, every package does more complicated probing of CPU capabilities, compiler and glibc support lacking
for instance __int128 support, etc. And the build times are so humongous, that testing some hypothesis or fixes just takes to long.

More importantly, most CPUs should really have SSE2 support nowadays, I can count people using the i686 branch probably with one hand. :-)

levi · 2020-01-31 07:38:01

True, but you could say the same for x64 instruction support CPUs with such abilities to my knowledge have been out for about 12 years now (and now I actually look it up you can add another 5 years to that), so even the second hand desktop machine running as my server runs Arch64 natively. I did wonder about the sense of releasing the i486 fork, but I guess someone with the ability to build packages had some old machines they wanted to support and there's always odd VIA chips and stuff that it turns out don't run the instruction codes you might expect given their vintage

abaumann · 2020-01-31 08:01:01

i486 was the idea to support Alix (my and deep42thouth's router), some old AMD machines not having SSE/MMX
and of course making MrBIOS happy with an OLPC-1 version of Archlinux32. But I admit not having done much on
that branch since bootstrapping it, too many packages just simply break or don't support i486. Main blockers there
are librsvg/rust and Xorg there.

levi · 2020-01-31 21:41:38

Ah yeah, while for a router, you can generally get away without much graphics, or any svg support, you'll at least need xorg for a olpc based on an AMD Geode or a VIA C7, not to mention some kind of graphical web browser.

And is is just me or has the title here changed to indicate our hapless OP has achieved a modicum of success? Colour me slightly surprised, but I'm impressed all the same!

sukolyn · 2020-02-01 02:40:34

And is is just me or has the title here changed to indicate our hapless OP has achieved a modicum of success?

yes. changing Architecture parameter in /etc/pacman.conf from auto to pentium4 "allowed" pacman to access chromium 79. you missed #12.

abaumann · 2020-02-01 08:09:51

I just wanted to reiterate the usual caveats:
- don't do partial updates, the packages are not guaranteed to work together..
- don't do partial architecture switches..

..unless of course you really know what you are doing and are not confused by the results. :-)

Arch Linux

#1 2020-01-28 22:02:00

[solved] libicui18n.so.64 missing

#2 2020-01-28 22:42:28

Re: [solved] libicui18n.so.64 missing

#3 2020-01-29 15:09:56

Re: [solved] libicui18n.so.64 missing

#4 2020-01-29 18:04:02

Re: [solved] libicui18n.so.64 missing

#5 2020-01-29 18:33:32

Re: [solved] libicui18n.so.64 missing

#6 2020-01-29 21:25:52

Re: [solved] libicui18n.so.64 missing

#7 2020-01-29 23:50:02

Re: [solved] libicui18n.so.64 missing

#8 2020-01-30 07:24:23

Re: [solved] libicui18n.so.64 missing

#9 2020-01-30 17:09:47

Re: [solved] libicui18n.so.64 missing

#10 2020-01-30 19:23:14

Re: [solved] libicui18n.so.64 missing

#11 2020-01-30 20:21:07

Re: [solved] libicui18n.so.64 missing

#12 2020-01-30 20:40:01

Re: [solved] libicui18n.so.64 missing

#13 2020-01-30 20:46:34

Re: [solved] libicui18n.so.64 missing

#14 2020-01-31 07:07:51

Re: [solved] libicui18n.so.64 missing

#15 2020-01-31 07:38:01

Re: [solved] libicui18n.so.64 missing

#16 2020-01-31 08:01:01

Re: [solved] libicui18n.so.64 missing

#17 2020-01-31 21:41:38

Re: [solved] libicui18n.so.64 missing

#18 2020-02-01 02:40:34

Re: [solved] libicui18n.so.64 missing

#19 2020-02-01 08:09:51

Re: [solved] libicui18n.so.64 missing

Board footer