hello my friend, try theMy tests show that both LxPup-15.05 and LxPupTahr-15.03 are not "modern" enough to run this version.....
Quote:
/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.20' not found
lib6+libstdc6-4.9.2.pet
hello my friend, try theMy tests show that both LxPup-15.05 and LxPupTahr-15.03 are not "modern" enough to run this version.....
Quote:
/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.20' not found
My tests show that both LxPup-15.05 and LxPupTahr-15.03 are not "modern" enough to run this version.....
Quote:
/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.20' not found
download lib6+libstdc6-4.9.2So we may be reaching the end of the Chromium versions that will run on LxPup and LxPupTahr
hi kost@skost@s wrote:hello my friend, try theMy tests show that both LxPup-15.05 and LxPupTahr-15.03 are not "modern" enough to run this version.....
Quote:
/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.20' not found
lib6+libstdc6-4.9.2.pet
Here's what I do....gcmartin wrote:Is there a utility which will keep Chromium current in PUPs?
Should you or anyone do so, bear in mind that the result is a pathway for making and keeping Chromium current. And, the resulting utility should reside in the Menu system somewhere. Just an idea.peebee wrote:... I suppose I could produce a small utility to automate the above scheme but that would mean standardising or locating the folder names (I think). Does a frugal install "know" the name of the folder it has been booted from??gcmartin wrote:Is there a utility which will keep Chromium current in PUPs?