Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Problem with libstdc

Message
Author
User avatar
radissthor
Forum Regular
Forum Regular
Posts: 339
Joined: Mon Sep 13, 2010 11:18 am

Problem with libstdc

#1 Post by radissthor » Mon Nov 16, 2015 8:59 am

Hi all,

I am running Mepis 12, but I have the same problem in an MX14 machine. I gave information about this problem in this thread, but because the initial topic was different I am continuing it here.

I am trying to run the latest version of praat but I get the following error message:

Code: Select all

./praat: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.18' not found (required by ./praat)
If I am reading this correctly, I need a different version of libstdc ?? I am not sure that is the case. Any assistance would be much appreciated, as I need to run praat for work :frown:

Cheers
Image

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9318
Joined: Wed Jul 12, 2006 2:26 pm

Re: Problem with libstdc

#2 Post by kmathern » Mon Nov 16, 2015 9:36 am

I see praat in the repos, though it's an older version (5.3.16) versus what you get from directly downloading it (6.0.05).

Code: Select all

$ apt-cache policy praat
praat:
  Installed: (none)
  Candidate: 5.3.16-1
  Version table:
     5.3.16-1 0
        500 http://httpredir.debian.org/debian/ wheezy/main i386 Packages
I would install and use the repo version if it works okay for you.

If you actually need the newer version, the sid source can probably be backported, it's still not the latest version but it's quite a bit newer than the Wheezy 5.3.16 version.

User avatar
radissthor
Forum Regular
Forum Regular
Posts: 339
Joined: Mon Sep 13, 2010 11:18 am

Re: Problem with libstdc

#3 Post by radissthor » Mon Nov 16, 2015 9:42 am

kmathern wrote:I see praat in the repos, though it's an older version (5.3.16) versus what you get from directly downloading it (6.0.05).

Code: Select all

$ apt-cache policy praat
praat:
  Installed: (none)
  Candidate: 5.3.16-1
  Version table:
     5.3.16-1 0
        500 http://httpredir.debian.org/debian/ wheezy/main i386 Packages
I would install and use the repo version if it works okay for you.

If you actually need the newer version, the sid source can probably be backported, it's still not the latest version but it's quite a bit newer than the Wheezy 5.3.16 version.
I am afraid I do need the latest version, since otherwise sound does not work on Linux. Could the sid package be backported to Mepis?
Image

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9318
Joined: Wed Jul 12, 2006 2:26 pm

Re: Problem with libstdc

#4 Post by kmathern » Mon Nov 16, 2015 9:53 am

radissthor wrote:...I am afraid I do need the latest version, since otherwise sound does not work on Linux. Could the sid package be backported to Mepis?
I think it can be backported, it looks like it has pretty simple build depends. One of the CR packagers (Stevo, Tim or Mike) will probably see this topic and do it for you.

User avatar
lucky9
Forum Veteran
Forum Veteran
Posts: 11380
Joined: Wed Jul 12, 2006 5:54 am

Re: Problem with libstdc

#5 Post by lucky9 » Mon Nov 16, 2015 10:24 am

Or Dot the i, and make a request. There's a sub-forum just for such use. It is checked by those involved.
Yes, even I am dishonest. Not in many ways, but in some. Forty-one, I think it is.
--Mark Twain

User avatar
mmikeinsantarosa
Forum Guide
Forum Guide
Posts: 2371
Joined: Thu May 01, 2014 10:12 am

Re: Problem with libstdc

#6 Post by mmikeinsantarosa » Mon Nov 16, 2015 10:50 am

I'll see if I can get praat (6.0.4-2) to go on m12 after work today. - mike
LT: MX17.1 Quad Core model: Intel Core i7-6820HQ Kernel: 4.16.0-12.1-liquorix-amd64 (64 bit)
DT: Intel(R) Core i5-3.1GHz Kernel~3.9-1-mepis64 x86_64

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16177
Joined: Fri Dec 15, 2006 8:07 pm

Re: Problem with libstdc

#7 Post by Stevo » Mon Nov 16, 2015 7:49 pm

Packages compiled against newer gcc versions, as in Sid, will often automatically require a newer version of that library. It's my guess that messing around with libstdc will result in a broken, dying system; that's why backporting something like praat is the best solution. Trying to force install a package from upstream Debian (or MX) is not a good idea.

User avatar
mmikeinsantarosa
Forum Guide
Forum Guide
Posts: 2371
Joined: Thu May 01, 2014 10:12 am

Re: Problem with libstdc

#8 Post by mmikeinsantarosa » Mon Nov 16, 2015 11:52 pm

I was able to get praat-6.0.4-2 to build and run in m12, not so for m11 and am working on packages for MX15. The link to the m12 set has been sent up. - mike
LT: MX17.1 Quad Core model: Intel Core i7-6820HQ Kernel: 4.16.0-12.1-liquorix-amd64 (64 bit)
DT: Intel(R) Core i5-3.1GHz Kernel~3.9-1-mepis64 x86_64

User avatar
radissthor
Forum Regular
Forum Regular
Posts: 339
Joined: Mon Sep 13, 2010 11:18 am

Re: Problem with libstdc

#9 Post by radissthor » Tue Nov 17, 2015 7:25 am

mmikeinsantarosa wrote:I was able to get praat-6.0.4-2 to build and run in m12, not so for m11 and am working on packages for MX15. The link to the m12 set has been sent up. - mike
Thanks for the info Mike. I am just curious as what the build of Praat entails, since they don't provide any .deb packages, but only an executable file. In any case, looking forwards to the MX15 build.

Many thanks!
Image

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16177
Joined: Fri Dec 15, 2006 8:07 pm

Re: Problem with libstdc

#10 Post by Stevo » Tue Nov 17, 2015 8:01 pm

I am just curious as what the build of Praat entails,
The beauty of backporting debianized source is that the backporter usually doesn't need to know what's going on under the hood--only if the normal backport recipe fails do we have to open it and get our hands dirty.

Even then, much of the detail work of making packages is now handled by debhelper, which has a good amount of heuristic AI.

Post Reply

Return to “General”