[SOLVED] Have glibc 2.13, need glibc 2.14 - what to do?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Recently I bought a new Arduino (µC). When I want to compile and upload a program, the IDE complains about glibc:
... version `GLIBC_2.14' not found ...
What can I do to have glibc 2.14 running? Would this be just some sort of "./configure; make; make install" or are the things more complicated?
Since disk space isn't such a big problem anymore I installed Fedora on a free partition - but I really don't want to move over to Gnome 3 and systemd.
I'm using fedora as an work-around. Just installed it, works.
What I have is an not-so-new debian wheezy 7: It has libc 2.13, the new Arduino IDE wants 2.14. Instead of moving to a newer debian I'd like to make it "glibc 2.14 capable" without breaking anything.
What I have is an not-so-new debian wheezy 7: It has libc 2.13, the new Arduino IDE wants 2.14. Instead of moving to a newer debian I'd like to make it "glibc 2.14 capable" without breaking anything.
wheezy is definitely and absolutely dead. You are on your own.
You need a separate install with a somewhat newer distro. don't have to be fedora/gnome/systemd.
There are systemd-less distros out there or if you are just trying to avoid Gnome, plenty of alternatives. Practically EVERY alternative runs circles around gnome anyway
The number of systemd-less distros is limited. The only one I found that is somewhat old, still alive and widely used is Slackware. But since Slackware's packet management doesn't offer dependency management I moved back to the wheezy I came from in Nov. '18.
So, it seems I simply *have* to move to a more actual distro. The question is if it's going to be debian 10 or fedora.
Understood - never used Fedora because it is simply too bleeding edge for me and has a short half life, lol. I use Void Linux which uses runit and it works very well. Debian is one of my favorite systemd distros. though, along with Arch.
edit:
Are you saying you want a "somewhat old" distro? Maybe Devuan fits your bill? (ducks and runs)
edit2:
Yes, it seems you are saying exactly that.
But aren't you really saying "something that follows a long-established paradigm and runs smoothly on my legacy hardware"? Because many of the distros on that link I gave fit that bill.
Nothing wrong with Devuan either.
edit:
Are you saying you want a "somewhat old" distro? Maybe Devuan fits your bill? (ducks and runs)
edit2:
Yes, it seems you are saying exactly that.
But aren't you really saying "something that follows a long-established paradigm and runs smoothly on my legacy hardware"? Because many of the distros on that link I gave fit that bill.
Nothing wrong with Devuan either.
No. What I was looking for when I decided not to upgrade from debian 7 to debian 8 was a distro that is free of systemd and pulse-audio, that was still alive and widely used. The only distro I found back in Nov. '18 was Slackware. Devuan looked good especially because it was using Gnome 2.
Anyway ... since I was forced to move to some actual distro I chose to upgrade to debian 10 a few days ago. I hope that will do for some years.
Void is actively maintained and is systemd free. I cannot recall whether it uses PulseAudio. It IS rolling though, so not without occasional issues, as with all other rolling release distros. The installer is also not the greatest if you are used to a pretty dialog wizard but is quite functional.
Gnome 2 no longer exists. What you are seeing was Mate`, which is a fork of Gnome2.
Last edited by sevendogsbsd; 01-17-2020 at 02:05 PM.
... Gnome 2 no longer exists. What you are seeing was Mate`, which is a fork of Gnome2.
I know. I really loved Gnome 2 since it was well configurable using console tools like pico. And I started to dislike Gnome 3 from the first moment - maybe the first release I saw was buggy. And I began to dislike it even more when I heard that the programmer of systemd and pulseaudio was part of the team that developed Gnome 3.
So, now I am trying Debian 10.2 (had to upgrade because of my new Arduino) with XFCE. If it runs good for the next few days I will try to use it as my new standard and change GRUB.
I'm really tired of fiddling around with system stuff. Had that since '96 with Linux, since '84 with an ZX 81.
No. What I was looking for when I decided not to upgrade from debian 7 to debian 8 was a distro that is free of systemd and pulse-audio, that was still alive and widely used.
Obviously you did not click the link I provided.
:shrugs:
Obviously you did not click the link I provided.
:shrugs:
There are actually quite a few items in that search - many are BSDs which are not Linux of course, but others I knew nothing about. I have always gone here and had not thought about the distrowatch search: https://nosystemd.org/
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.