/var/lib/boinc-client/slots/28/build/cmdock: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /var/lib/boinc-client/slots/28/build/libcuriedock.so.0)

Are there other requirements?

/var/lib/boinc-client/slots/28/build/cmdock: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /var/lib/boinc-client/slots/28/build/libcuriedock.so.0)

Are there other requirements?

No, should be only GLIBC_2.27. RxDock application doesn't need that. We make tasks for it, too.

Here is a workaround for openSUSE Leap (glibc 2.26) users:

When it became known that Universe@home benefits substantially from glibc 2.29 and later, I copied libm and libmvec version 2.31 from openSUSE Tumbleweed onto my openSUSE Leap computers.

I am receiving CurieMarieDock tasks and they complete fine.

This is what I did:

• download glibc-2.??-*.x86_64.rpm from https://download.opensuse.org/tumbleweed/repo/oss/x86_64/
  
• in a temporary directory, extract the rpm file: rpm2cpio glibc*.rpm | cpio -idmv
  
• copy libm and libmvec into the library load path, e.g.: sudo cp -p libm-2.??.so libmvec-2.??.so /lib64/
  
• stop boinc: sudo service boinc-client stop
  
• register the new library versions: sudo ldconfig
  
• restart boinc: sudo service boinc-client start
  

* * * * W A R N I N G * * * *

Mixing library versions in this way is dangerous and completely unsupported. It can make your system unusable. Don't do it unless you know how to detect whether or not possibly occurring problems are caused by this workaround, and unless you know how to restore your system to the distributor's glibc version.

I chose this nasty hack because it appeared a lot easier to perform than a proper glibc version update.

Some time after I performed this workaround, Tumbleweed advanced from glibc 2.31 to 2.32. I have not tried if my workaround works with 2.32 too.

Hi!

Very interesting hack! :-)
Will such a thing be possible with Ubuntu/Debian too?
Here on the Debian branch we're using .deb packages,
and I must admit that I'm mostly used to install them directly by using apt-get
(and dpkg for some older versions of FPC/Lazarus) so I'm not sure I understand
how to extract the files from within a .deb package.

//Gunnar

As I wanted to run all applications I could, I decided to take the upgrade path rather than any hacks.
This seemed a good idea at the time, so I went ahead with it.

I started with Fedora 23 which has GLIBC 2.22
Went to Fedora 25 which has GLIBC 2.24, this seemed to go OK.
So jumped with confidence to Fedora 27 which has GLIBC 2.26, again seemed to go OK
Confidence still high started Fedora 29 download (Fedora 28 has GLIBC 2.27) with GLIBC 2.28
All seemed OK with download and install of updates till the reboot, would not get past first boot up screen.
OH NO I though what have I done?

Long story shortened, 18 hours later I found a way via editing the BOOT menu to get the GUI back and then Fedora
tells me "Congratulations Fedora 29 update complete",,, What.
Anyway I am too scared to reboot again Linux Fedora 29 is running with GLIBC 2.28 and I can launch BOINC, CurieMarieDock work units have been running fine.

I still can't get the BOINC Manager to work, all files appear to be there, but nothing happens when I launch it, so I can't see what is running unless I check Task Manager.

(I launched BOINC directly from the BOINC folder using boinc executable, the boincmgr executable is the one not launching.
So 2 days to get back up and running (mostly), but it has been a learning experience,

I should do single version upgrades of the OS not multiples, less time and less things to go wrong.

Backup your data, I didn't but was lucky as it all stayed there and I didn't lose anything.

Don't leave it so long to upgrade (I will still probably leave it as I don't plan on upgrading every 6 months, if it works don't touch it)

Make sure you have a lot of hot Tea (or Coffee if you prefer), food or snacks available as it will take a long time to do multiple updates.

Onward with the fun of computing (I will laugh about this sometime in the future I am sure).

Conan

Gunnar Hjern wrote:

Will such a thing be possible with Ubuntu/Debian too?

While I have some computers with Debian based OS too (Mint), I have very little experience using these. I treat these computers as appliances and rely a lot on advice from team mates in matters of administration of this OS.

According to a web search, the contents of a .deb package can be extracted (not installed) with:
dpkg --extract file.deb temporarydirectory/

Hi!

Thanks for the info on dpkg!!

In order to test running the Universe@home project on an older computer I really did make a try this week with taking the files:
libm-2.27.so libstdc++.so.6.0.25 libmvec-2.27.so and symlinks: libmvec.so.1 libstdc++.so.6
from an Ubuntu-18 machine and put them all in the project directory for the U@H project, i.e.:
/var/lib/boinc-client/projects/universeathome.pl_universe/

That went fine (once I also created the symlinks) and that old can crunched Universe all night w/o errors. :-)
By placing the files in the project directory I don't risk compromising the rest of the system.

I haven't tried this with SiDock yet as I've been too busy the rest of the week,
but should there be a shortage of rxDock tasks I'll try this trick here too.

//Gunnar

This explains why all my tasks end with computing error (I'm translating). I don't feel comfortable modifying glibc on my system because it's a quite important library, so I'm going to wait for my distro's upgrade. See you in June.

I am being bitten by this too, as I am a long time openSUSE user and am on Leap 15.2. Is this a hard requirement or can you compile to target 2.26 and later?

---

As I wanted to run all applications I could, I decided to take the upgrade path rather than any hacks.
This seemed a good idea at the time, so I went ahead with it.

I started with Fedora 23 which has GLIBC 2.22
Went to Fedora 25 which has GLIBC 2.24, this seemed to go OK.
So jumped with confidence to Fedora 27 which has GLIBC 2.26, again seemed to go OK
Confidence still high started Fedora 29 download (Fedora 28 has GLIBC 2.27) with GLIBC 2.28
All seemed OK with download and install of updates till the reboot, would not get past first boot up screen.
OH NO I though what have I done?

Long story shortened, 18 hours later I found a way via editing the BOOT menu to get the GUI back and then Fedora
tells me "Congratulations Fedora 29 update complete",,, What.
Anyway I am too scared to reboot again Linux Fedora 29 is running with GLIBC 2.28 and I can launch BOINC, CurieMarieDock work units have been running fine.

I still can't get the BOINC Manager to work, all files appear to be there, but nothing happens when I launch it, so I can't see what is running unless I check Task Manager.

(I launched BOINC directly from the BOINC folder using boinc executable, the boincmgr executable is the one not launching.
So 2 days to get back up and running (mostly), but it has been a learning experience,

I should do single version upgrades of the OS not multiples, less time and less things to go wrong.

Backup your data, I didn't but was lucky as it all stayed there and I didn't lose anything.

Don't leave it so long to upgrade (I will still probably leave it as I don't plan on upgrading every 6 months, if it works don't touch it)

Make sure you have a lot of hot Tea (or Coffee if you prefer), food or snacks available as it will take a long time to do multiple updates.

Onward with the fun of computing (I will laugh about this sometime in the future I am sure).

Conan

Have a look in your home directory for a file called Boinc-Manager-xxxx or similar, it should be 5 bytes long.

If you find it then delete it, it’s a lock file to say that BM is running but it sometimes gets left behind when it closes.

Problem:
<stderr_txt>
../../projects/www.sidock.si_sidock/cmdock-boinc-zcp_wrapper_2.1_arm-unknown-linux-gnueabihf: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not found (required by ../../projects/www.sidock.si_sidock/cmdock-boinc-zcp_wrapper_2.1_arm-unknown-linux-gnueabihf)
</stderr_txt>

Is there an easy way to install or update GLIBC on Ubuntu 18.04.4 LTS [3.16.60-28|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1.2)] ? Its an ARM device.

If Ubuntu20LTS (Updated to LTS Kernel 3.16.82) will have the matching GLIBC version I would directly upgrade Ubuntu, but the kernel is still 3.16 - maybe the GLIBC also stays old...

Hi Magiceye04,

I've identified your device as being a Hardkernel Odroid-C2.

Armbian has an Armbian 24.11.1 Noble Gnome image for it, with kernel 6.6.61