Skip to main content

WARNING: C++ compiler too old, need g++ 4.8 or clang++ 3.4 (CXX=g++)

By Er.Susheel


If you ever worked on GULP installation as System Admin on Linux Servers, you might had come across below error 

Error:   "WARNING: C++ compiler too old, need g++ 4.8 or clang++ 3.4 (CXX=g++)"
Solution:  To Solve this error we need to install newer version of C++ and g++ rpm packages on linux servers. Try to get the exact version which error message is saying to you on screen.

 Or You can Download below rpm files for RHEL6/CENTOS6 operating System and then install it

       # yum install scl-utils 

 ======================================================================

                                        If this resolve your error, you can 

  • Subscribe to My YouTube Channel  
  • Ask Me for any Linux Freelancer Work
  • Buy Cheapest SSL certificate for your Domains at My Hosting Website
  • Buy Cheapest Webhosting Packages for Cpanel 
  • Buy Cheapest Webhosting Packages for Linux and Windows Dedicated Boxes


Linuxforeveryone started with the focus of solving linux related issues a sys admin faces everyday. So as System Admin whatever i learn through my experience i try to write it down for rest of opensource community.

If you appreciate what you have read or this blog writeup helped you can considering buying me COFFEE, this will help me keep writing and helping community further.

   

Labels:

Comments

Post a Comment

Popular posts from this blog

Solution and Step to fix CVE-2019-5736 Vulnerability - Docker

By Linux For Every One
Recently a new vulnerability has been discovered in the the internet market having target to Docker services. What is this Vulnerability: In short, Docker service uses another service called as runc which is container run time to spawn and run containers. which simply means if docker task is to create docker images then runc task would be running them and attaching a process to container. So as per the recent discovery by the maintainers of runc, the code of this service was having some bug which can be used by attackers to gain the root level of access of the host machine on which docker containers are running. How it can be Exploited: This vulnerability can be exploited in two ways (1) if the docker images are in use is vulnerable making the containers build from it vulnerable also (2) if somehow attacker got the access of containers and then trying to exploit using the bug present in runc and trying to get root privileges. Solution to Fix Vulnerability: Ce
1 comment
Read more

Linux Bug - Dirty COW

By Er.Susheel
Recently World of Linux come across yet another bug which is haunting the nix users all over the world. This bug has given a name COW and its associated CVE number is CVE-2016-5195. Its kind of funny how this bug get their names, this too grab my attention when i first heard about it as COW ! i laughed out like what ? :) For Freelance Work & Queries Contact me by Email Id support@linuxforeveryone.com Background : later when I started reading about this bug in details got to know how this bug got his name, which nothing but a " copy-on-write " technique which Linux kernel uses to maintain the private read -only memory mapping and this technique have some flaws in it since 2007 woohooo that was way long back. In other words if i have to say is this bugs allow a server to become completely compromised through local privilege escalation. This vulnerability is specific to the Linux Kernel, and exploiting this vulnerability does require a local system user
22 comments
Read more

Multiple instances of redis

By Er.Susheel
In the last post I have covered how to install redis server on Centos/Rhel using rpm method and yum method and some troubleshooting skills. In this post i am going to cover how to install and configure redis to run with multiple ports.                                                                           But why we need more ports ? If you have read my earlier post , you already know that by default redis runs on single port 6379, which any one can use it for small website to cache the data. But for heavy website like magento we need to use additional ports along with 6379 to serve different cache from different ports. Like in Magento there is simple cache which is normally stored under /var/cache directory. Then there is Full Page Cache which is stored under /var/full_page_cache and session cache which is stored under /var/session_cache. Note : Discussion about cache/full page cache/session is not under the scope for this document.                      
35 comments
Read more