Arch Linux

festuc

Member

Registered: 2017-02-04

Posts: 6

recompiling a aur package mldonkey

I was instaled mldonkey few moths ago, but now distro uses a new glib and apears this notice
This core is running with glibc 2.28 but it was compiled with glibc 2.26.
Often mlnet don't start just say i can not, and stop it
So i try with yay uninstall and install mldonkey but yay no compile, i guess i have a last compilation But i dont see whatever is located.
So how can i build a new package from aur with glibc 2.28?

Morganamilo

Package Maintainer (PM)

Registered: 2017-12-05

Posts: 77

Re: recompiling a aur package mldonkey

Please don't bother the forums with questions about yay. See: https://github.com/Jguer/yay#support

Although there's no need for support as the manpage already has a solution.

So how can i build a new package from aur with glibc 2.28?

This makes me think you shouldn't be using an AUR helper in the first place. See
the wiki pages for makepkg and compile it manually.

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 13,709

Website

Re: recompiling a aur package mldonkey

mldonkey is not an AUR package, I have no idea whether yay has any ABS capabilities..

I doubt the glibc discrepancy is causing you any issues, but if you want to check whether a recompilation helps, see https://wiki.archlinux.org/index.php/Arch_Build_System

Otherwise, please provide more information about your actual issue -- why mlnet fails. Check if it has a debug mode, and post any messages it generates. If it has a log, post that.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: recompiling a aur package mldonkey

The version of glibc does not matter, glibc provides the exact same library version since 1997 and it's possibly the only library which it is *always* safe to upgrade.

Later versions of glibc should never, ever, ever be incompatible with old versions. Only new symbols are added, old symbols do not get dropped. The goal of the glibc developers is that any binary ever compiled using libc.so, will continue working on newer distros no matter what.

If mldonkey contains code to provide such a warning, that is incredibly silly of them, and it should definitely be ignored.

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

loqs

Member

Registered: 2014-03-06

Posts: 19,111

Re: recompiling a aur package mldonkey

@eshwartz http://cvs.savannah.gnu.org/viewvc/mldo … 0&r2=1.61&